Direct API

Your servers send the content; Adzen sends back a ready-to-render ad.

Use the API when you want to decide when matching happens and how the ad is drawn — or when your content never appears on a browser page in a form the tag can serve.

Every surface shares the same pattern:

1. Send the content to the surface’s endpoint.
2. Receive a matched ad, or a no-match response.
3. Render the ad, and fire its pixel_trackers URLs once it is actually visible on screen.

A no-match is a normal response. It means nothing cleared our relevance and brand-safety bar for that content. Render your default state; do not retry. On UGC it can be an empty ads array or { "no_ad_retry_after_seconds": N }, which has no ads field. See No match.

Endpoint by surface

Shared by every surface

• Authentication
• Sandbox — schema-correct responses, never billed
• Rate limits