Guide

Authentication & API keys

Authenticate requests with your API key or a job token.

The API uses key-based authentication sent in HTTP headers. There is no OAuth flow — you pass your key (or a job token) directly on each request.

Getting an API key

Generate an API key from your api2convert account. Keep it secret: anyone with the key can create jobs and consume your credits.

API key header

Authenticate user-level requests with the x-oc-api-key header:

curl https://api.api2convert.com/v2/jobs \
  -H "x-oc-api-key: <your-api-key>"

Job tokens

Each job also has a token. A token grants access to that single job only and can be used in place of the API key via the x-oc-token header — useful for handing a client temporary, scoped access to one job.

curl https://api.api2convert.com/v2/jobs/<job-id> \
  -H "x-oc-token: <job-token>"

Public endpoints

A few read-only endpoints need no authentication, including GET /v2/conversions, GET /v2/presets and GET /v2/statuses.

Free vs. paid

Every registered user gets 30 free credits every 24 hours; paid plans add higher quotas for professional use. Your plan determines quotas and concurrency — see Rate limits & contracts.

Never embed your API key in client-side code or public repositories. For browser/native clients, proxy requests through your backend and hand out per-job tokens.