> ## Documentation Index > Fetch the complete documentation index at: https://docs.extole.com/llms.txt > Use this file to discover all available pages before exploring further. # Render With Data > Renders this content for the person making the request, merging the targeting data in the body into what the zone is given. ## OpenAPI ````yaml /feature-specific-apis/call-to-action.json post /zones/call_to_action openapi: 3.1.0 info: title: Call To Action version: 1.0.0 description: >- Operations published by Extole Call To Action components. Generated from the component contracts on my.extole.com. servers: - description: Production - Extole API host url: https://api.extole.io - description: Production - your program domain url: https://{brand}.extole.io variables: brand: default: yourcompany description: >- Your Extole client subdomain (e.g. 'mycompany' for mycompany.extole.io) security: [] paths: /zones/call_to_action: post: tags: - VIEW summary: Render With Data description: >- Renders this content for the person making the request, merging the targeting data in the body into what the zone is given. operationId: render_with_data requestBody: required: true content: application/json: schema: type: object properties: email: type: string format: email description: Email address of the person to render for. last_name: type: string description: Last name of the person to render for. first_name: type: string description: First name of the person to render for. description: >- Targeting data merged into the zone's rendering context. Keys are open - recognised fields such as email, first_name and last_name target the render, and anything else is passed through to the creative. additionalProperties: true responses: '200': description: Success content: application/json: schema: description: >- Rendered zone content. The shape follows the zone's creative configuration: HTML, JavaScript, JSON, or plain text. '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/RestExceptionResponse' examples: binding_error: $ref: '#/components/examples/binding_error' invalid_json: $ref: '#/components/examples/invalid_json' invalid_parameter: $ref: '#/components/examples/invalid_parameter' missing_request_body: $ref: '#/components/examples/missing_request_body' '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/RestExceptionResponse' examples: access_denied: $ref: '#/components/examples/access_denied' expired_access_token: $ref: '#/components/examples/expired_access_token' invalid_access_token: $ref: '#/components/examples/invalid_access_token' jwt_authentication_error: $ref: '#/components/examples/jwt_authentication_error' method_unauthorized: $ref: '#/components/examples/method_unauthorized' missing_access_token: $ref: '#/components/examples/missing_access_token' security: - HEADER: [] - QUERY_PARAM: [] - COOKIE: [] servers: - description: Production - your program domain url: https://{brand}.extole.io variables: brand: default: yourcompany description: >- Your Extole client subdomain (e.g. 'mycompany' for mycompany.extole.io) components: schemas: RestExceptionResponse: type: object description: Represents the API error response properties: code: type: string description: Specific error code for this error type, documented per endpoint http_status_code: type: integer description: >- HTTP status code that was returned with this error, useful if client get response code message: type: string description: User readable English description of the error parameters: type: object description: >- Attributes related to the error, varies be error code, documented per endpoint additionalProperties: type: object description: >- Attributes related to the error, varies be error code, documented per endpoint unique_id: type: string description: >- Unique id associated with this error, useful for discussions with Extole required: - code - http_status_code - message - parameters - unique_id examples: binding_error: summary: binding_error value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 400 code: binding_error message: Argument is not of the expected type parameters: {} invalid_json: summary: invalid_json value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 400 code: invalid_json message: JSON is invalid parameters: {} invalid_parameter: summary: invalid_parameter value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 400 code: invalid_parameter message: Parameter is invalid. parameters: {} missing_request_body: summary: missing_request_body value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 400 code: missing_request_body message: Missing request body parameters: {} access_denied: summary: access_denied value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 403 code: access_denied message: >- The access_token provided is not permitted to access the specified resource. parameters: {} expired_access_token: summary: expired_access_token value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 403 code: expired_access_token message: The access_token provided with this request has expired. parameters: {} invalid_access_token: summary: invalid_access_token value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 403 code: invalid_access_token message: The access_token provided with this request is invalid. parameters: {} jwt_authentication_error: summary: jwt_authentication_error value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 403 code: jwt_authentication_error message: The jwt authentication failed. parameters: {} method_unauthorized: summary: method_unauthorized value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 403 code: method_unauthorized message: Access forbidden to this endpoint parameters: {} missing_access_token: summary: missing_access_token value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 403 code: missing_access_token message: No access_token was provided with this request. parameters: {} securitySchemes: HEADER: type: apiKey in: header name: Authorization description: >- A consumer access token, issued to a single person in the browser or app. Not a client access token - never send a client token from a consumer device. x-bearer-format: bearer QUERY_PARAM: type: apiKey in: query name: access_token description: >- A consumer access token, issued to a single person in the browser or app. Not a client access token - never send a client token from a consumer device. COOKIE: type: apiKey in: cookie name: extole_token description: >- A consumer access token, issued to a single person in the browser or app. Not a client access token - never send a client token from a consumer device. ```` ## Related topics - [Render With Data](/api-reference/feature-specific/experience/view/render-with-data.md) - [Render](/api-reference/feature-specific/page-creative/view/render.md) - [Render a zone with targeting data](/api-reference/content/render-a-zone-with-targeting-data.md) - [Render a zone with the name and targeting data in the body](/api-reference/content/render-a-zone-with-the-name-and-targeting-data-in-the-body.md) - [Render a zone](/api-reference/content/render-a-zone.md)