Render a zone with the name in the body

Renders a zone using a request body that carries both the zone name and the targeting data. Functionally equivalent to POST /v5/zones/{zone_name}; the path-based form is the recommended primary entry point. Use this form when the calling code constructs the full request payload upstream and prefers a single body shape. Returns the zone's configured content (HTML, JavaScript, JSON, or plain text) plus X-Extole-* headers describing the matched campaign and creative. Authenticated with a USER_SUPPORT scope access token.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

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.

string
required

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

Headers
string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Responses
200

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).

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json