Copy page

Start here

Authentication

Send your API key on every data request using the HTTP Authorization header:

Code
Authorization: Bearer YOUR_API_KEY

Sign in, select a plan on the pricing page, then open My Subscriptions. Each subscription includes an API key. Reveal or copy the current key from its subscription page.

Production and sandbox API keys are separate. A sandbox key cannot authenticate a request to the production gateway. Paid plans on the production portal use real billing.

Authenticate a request

With the environment variables from the quickstart:

Code
curl "$ATM_API_BASE_URL/movies?limit=1" \
  --header "Authorization: Bearer $ATM_API_KEY"

Do not send keys in query parameters. URLs can appear in logs, browser history, and analytics.

Keep the key on your server

For a website or mobile application, have your backend call the API and return the data your client needs. Store the key in your server's secret manager or private environment configuration.

Do not bundle it into browser JavaScript, a public repository, a mobile binary, or a screenshot. A key embedded in a distributed app can be extracted. Apply your own access controls and request limits to the backend route that calls this API.

Use the reference explorer

Open an endpoint in the API reference and enter your key in its authorization control to try a request. Use your own key, and clear it before sharing your screen or device. Examples in these guides intentionally contain placeholders.

Diagnose an authentication failure

Repeated retries will not fix rejected credentials. Check configuration first. If a key is exposed, roll it from My Subscriptions, update your server configuration, and remove the exposed key. The portal shows any overlap period for the previous key.

Next: Search for a movie →