Skip to main content

Authentication

The partner API authenticates every request with an API key sent as a Bearer token. There are no sessions, cookies, or CSRF tokens to manage — each request carries the key.

Your two API keys​

Each account has two API keys, and the key you authenticate with selects how the job is handled:

KeyJob typeBilling
Metered keyBest-effort renders, no SLA, subject to system loadMetered per rendered hour
Reserved keyPriority renders, claimed ahead of best-effort workCovered by your provisioned dinks (flat monthly)

Both keys are UUIDs tied to your account, for example:

3f8c1a2b-9d4e-4f6a-bc12-7e0a5d9c1234

The reserved key only works while your account has provisioned dinks (reserved render nodes). A reserved request from an account with no dinks returns 403. If you only use best-effort rendering, use the metered key.

Treat both keys like passwords:

  • Keep them server-side. Never embed a key in client-side JavaScript, mobile apps, or anything a user can inspect — anyone holding a key can submit billable render jobs on your account.
  • Send them only over HTTPS.
  • Store them in a secret manager or environment variable, not in source control.

Account activation​

New accounts start in an inactive state. We reach out and activate your account before the API accepts any requests — until then, calls authenticated with your key are rejected. If you have signed up but your requests are returning 401, your account is most likely still pending activation.

Sending the key​

Pass the key in the Authorization header using the Bearer scheme on every request:

Authorization: Bearer YOUR_API_KEY

For example:

curl https://dinkem.gg/api/clips \
  -H "Authorization: Bearer 3f8c1a2b-9d4e-4f6a-bc12-7e0a5d9c1234" \
  -H "Content-Type: application/json" \
  -d '{ "demo_url": "https://example.com/demo.dem", "steam64_id": "76561198000000000", "round": 5 }'

Authentication errors​

Authentication failures return a JSON body with HTTP 401:

{ "error": "Missing or invalid API key" }
CauseResponse
No Authorization header, or it is not a well-formed Bearer <uuid>401 { "error": "Missing or invalid API key" }
Key does not match any account, or the account is not active401 { "error": "Invalid API key" }
Reserved key used by an account with no provisioned dinks403 { "error": "No reserved capacity provisioned" }

If you are confident the key is correct but still receiving 401, check that your account has been activated. A 403 on the reserved key means you have no provisioned dinks — use the metered key, or contact us to reserve capacity.

Once you can authenticate, head to Submitting Render Jobs.