RAWG Video Games Database | Operate As Docs

Connect your client's RAWG Video Games Database with a key they paste, and call its API through Operate As.

Website: rawg.io
Connects by: Pasting a API key
Category: Social and video
Services: 1
Tools: 30

Service	Key	Base URL
RAWG Video Games Database	`rawg`	`https://api.rawg.io/api`

Connecting

Your client makes a API key in their RAWG Video Games Database settings and pastes it on their link. Operate As tries it with RAWG Video Games Database 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": [
      "rawg"
    ]
  }
]

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

Permissions

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

Tools

Install RAWG Video Games Database's typed package for your language:

pip install operate-as-rawg

pip install operate-as-rawg

Run rawg.creator_roles_list

curl -X POST https://api.operate.as/v1/actions/rawg.creator_roles_list \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {}
  }'

curl -X POST https://api.operate.as/v1/actions/rawg.creator_roles_list \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {}  }'

Every input, with its JSON Schema: GET /v1/actions/rawg.creator_roles_list

Response

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

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

Pass-through

Paths continue from https://api.rawg.io/api. 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-.../rawg/games" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../rawg/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"}

When access ends

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

See Keeping access alive and Removing access.

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"}