Skip to main content
POST
Render a zone with the name in the body

Authorizations

Authorization
string
header
required

Body

Request body for POST /v5/zones. Carries both the zone name to render and an open data map of identity and targeting fields.

data
object
required

Open targeting data map merged into the rendering context. Recognised identity keys are email, partner_user_id, person_id, and event_time (ISO 8601). Additional keys are forwarded to the zone's targeting evaluator and creative renderer.

zone_name
string
required

Name of the zone to render. Must match a zone configured on the client account.

Example:

"global_header"

Response

Rendered zone content. The response body shape varies by the zone's creative configuration: HTML, JavaScript, JSON, or plain text. X-Extole-* response headers carry the matched campaign, frontend controller, creative, creative version, and input event identifiers, plus optional debug logs (X-Extole-Log).