Skip to main content
Every Simkl API request needs three URL parameters that identify your app, plus a User-Agent header. Endpoints that read or write user data also need an Authorization: Bearer token.

Required URL parameters

Append these to every request URL — both public catalog calls and authenticated user calls:
These three parameters help us see which apps are using the API, debug issues you report, and route around outages. They’re cheap to send — please always include them.

Required HTTP headers

As an alternative to the client_id query parameter, you may pass it as a simkl-api-key header. Either works; query-param form is preferred because it makes the request fully self-describing in URL form.

Putting it together

A typical authenticated call looks like:
A typical public call looks like:
In the API Reference playground these values are auto-filled — paste your client_id, app-name, app-version, and access_token once and they’ll be reused.

HTTP verbs

The full list of status codes Simkl returns lives on the Errors page.