---
title: "Render a named zone"
method: POST
path: "/api/v6/zones/{event_name}"
tags: ["Content"]
---

# Render a named zone

`POST /api/v6/zones/{event_name}`

API-friendly zone rendering at `POST /api/v6/zones/{event_name}`. Intended for backend rendering where the caller supplies a bearer access token directly. Renders the zone identified by the `event_name` path parameter and returns the structured zone content as JSON. Pass zone input data in the request body. Returns an error when no content backs the zone. For browser or in-app rendering use `POST /zones/{zone_name}` instead.

## Path parameters

- `event_name` string, required

## Request body

- object

## Response `200`

Zone content.

- ZoneResponse
  - `campaign_id` string, required — Extole campaign id that served this zone. Absent if not determinable.
  - `data` object, required — Creative output for this zone. Structure varies by campaign configuration.
  - `event_id` string, required — Extole event id generated for this zone render request.

## Other responses

- `400` — Zone rendering failed: `invalid_zone_name` if the zone name from the URL path is not recognised by the client's campaign configuration, or `invalid_creative_result` if the configured creative did not return valid JSON.
- `401` — Unauthorized
- `403` — Forbidden
- `415` — Unsupported Media Type
- `429` — Too Many Requests

---

[API](https://skmtc.net/extole/apis/integration-api-server-to-extole.md) · [All operations](https://skmtc.net/extole/apis/integration-api-server-to-extole/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/extole/integration-api-server-to-extole/revisions/c16e62e66755/schema)