Configure request parameters, data, and body

Separate configuration from conversational data

A request combines fixed values you define with variable data collected by the agent. Keeping them separate makes behavior predictable.

URL parameters

Enter a JSON object for query-string values.

{"status":"open","source":"inceptiva"}

Headers and base body

Use Headers for public values such as Accept or Content-Type. For POST, PUT, and DELETE, the base body contains fixed request values.

{"source":"virtual_agent","priority":"normal"}

Agent-collected data is added without replacing these values.

Data the agent must collect

Define an object whose keys are identifiers and values explain the expected data.

{"customer_email":"Customer email address","request_reason":"Detailed reason for the request"}

Keys must begin with a letter and contain only letters, numbers, or underscores. Every configured field is required.

Request only essential information. The agent can reuse data already present in the conversation.