Delivery endpoints
These endpoints are called by the Adzen tag running in the end user’s browser, not by your server. You do not integrate against them directly; they are listed so you can recognise the traffic your pages generate and allow it through your Content Security Policy.
All of them sit under /dea on the same host as the rest of the API:
https://api.adzen.ai/dea/...Endpoints
| Endpoint | Method | What it does |
|---|---|---|
/dea/url/keywords | POST | Fetches ads for the current page |
/dea/url/placements | POST | Requests ad placements for the current page |
/dea/url/impression | POST | Display-ad impression beacon |
/dea/url/placements/failures | POST | Reports a placement that failed to render |
/dea/url/hover | POST | Hover engagement signal |
/dea/ugc/impression | GET, POST | UGC ad impression beacon |
/dea/health | GET | Liveness check |
Allow CORS preflight
Every POST from the browser is preceded by an OPTIONS preflight. If you set
a Content Security Policy, allow api.adzen.ai in connect-src, and make sure
no proxy or firewall blocks OPTIONS requests to it. If the preflight fails,
the browser never sends the real request and no delivery call succeeds.
Partner APIs are a different surface
The endpoints above are the delivery path. The APIs you call from your own
backend are documented separately and use X-API-Key:
- UGC —
POST /v1/ugc/process - AI —
POST /v1/ai/process - Ad Manager — coming soon