IGDB | Operate As Docs

Connect your client's IGDB with a key they paste, and call its API through Operate As.

Service	Key	Base URL
IGDB	`igdb`	`https://api.igdb.com/v4`

Your client also types their twitch client id (In the Twitch developer console, under your application).

Connecting

Your client makes a Twitch client secret in their IGDB settings and pastes it on their link. Operate As tries it with IGDB before saving it, and stores it encrypted. See Services connected with an API key.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "igdb"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "igdb"    ]  }]

What the client reads	Permission it asks for
Use the IGDB key you paste, with only the access you gave that key	Chosen on the provider's screen

IGDB has no ready-made tools yet. Call any endpoint of its API through Operate As instead, with the client's access attached.

In Clients, add your client and select IGDB. Then send them their link.

They paste a Twitch client secret from their IGDB settings.

Pick the call from IGDB's own API docs. Your path is everything after https://api.igdb.com/v4.

Use the client's ID, the service key igdb and that path. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../igdbPOST /games" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../igdbPOST /games" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

A key works until your client deletes it in IGDB. They can paste a new one on the same link at any time, and your workflows carry on without changes.

Calls answer, once the key is deleted

{
  "status": 401,
  "data": {
    "…": "the service's own error"
  },
  "encoding": "json"
}

{  "status": 401,  "data": {    "…": "the service's own error"  },  "encoding": "json"}