Skip navigation

API authentication

How to send and safely store Kinescope API access tokens.

Authentication

Almost every request to the Kinescope API must carry a valid access token in the Authorization header — the one checked exception is GET /v1/dictionaries/timezones, which answers without one. Tokens are issued in the dashboard (Settings → API) and are scoped to a single workspace.

curl -H 'Authorization: Bearer <ACCESS_TOKEN>' \
  https://api.kinescope.io/v1/videos

Keep the token out of client-side code — anyone who sees it can act as the workspace owner until it is revoked. Create a separate token per integration so you can rotate or revoke any of them without disrupting the others.