Authentication

Every request to the Adzen API must include your API key in the X-API-Key header.


POST /v1/ugc/process HTTP/1.1
Host: api.adzen.ai
X-API-Key: your-api-key
Content-Type: application/json

Never commit API keys to source control. Store them in environment variables or a secrets manager.

Getting a key

Contact your Adzen account representative, or contact Adzen , to be onboarded.
You are issued a key scoped to a single product — UGC, AI, or Ad Manager. A key for one product is rejected on the others.

A missing, invalid, or wrong-product key fails with 401.

Endpoints that need no key

Each product exposes a health endpoint that is deliberately unauthenticated, on both production and sandbox:


GET https://api.adzen.ai/v1/ugc/health
GET https://api.adzen.ai/v1/ai/health

They return 200 ok. Use one to confirm you can reach the environment before you start debugging a key — a 401 proves you reached us and the key was rejected, while a connection failure or 404 means the request never arrived or the path is wrong.

Key rotation

Rotation is performed by Adzen — ask your account representative. There is no self-service rotation endpoint.

Read the key from an environment variable or secrets manager so it can be swapped without a redeploy when rotation happens.