Integration Overview
Adzen matches a contextual ad to each piece of user-generated content (a post, comment, or thread) and returns a ready-to-render ad payload. Your platform calls three endpoints at different points in the ad lifecycle.
The three core endpoints
| Endpoint | When to call |
|---|---|
POST /ugc/process | When a user creates a post or views a thread. Returns the matched ad. |
POST /ugc/impression | When the ad becomes visible on screen (MRC-compliant viewability). |
POST /ugc/disable | When a user dismisses or reports an ad. |
End-to-end flow
Two environments
| Sandbox | Production | |
|---|---|---|
| Base URL | https://sandbox.adzen.ai | https://api.adzen.ai |
| Responses | Hardcoded fake ads | Real matches from the live index |
| Billing | Never charged | Per-impression or per-click |
| Key prefix | sandbox- | prod- |
Use sandbox to prove out your integration before touching production keys. The response schema is identical between environments — if your client works in sandbox, it will work in production.