Skip to main content
POST
Build Agent Configuration
Read only Build Agent Configuration uses your workspace API key. Generates a draft configuration from structured answers. This operation does not save or publish an agent.

Before you begin

Use a server-side API key for the intended workspace.

Build Agent Configuration request

The request panel lists supported query parameters and body fields. For a request body, the example below supplies the required fields. Replace sample values with your own inputs.

Verify the result

Expect HTTP 201. Read the data property in the success envelope; the response panel documents its fields. Inspect data.status: needs_input requires answers to missingQuestions; human_review requires review of the evaluation; failed includes an error. completed provides draftAgent. Review its configuration, then map the fields into Create Agent. A build never publishes an agent automatically. A build can take longer than the 60 second HTTP timeout. For long builds, use Stream Agent Build, which keeps the connection open until the result is sent. This operation also accepts the matching /v1/assistant path. The request and result contracts are shared. Use one path consistently for your integration.

Retry safety

This operation does not modify workspace resources. Retry after a transient connection failure.

Errors and recovery

  • 401: Missing, expired, or invalid API key.
  • 400: The body failed validation, for example build_attempt outside 1 to 2 or an unknown pipeline. The message lists each problem.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
structured_input
object
required

Structured blueprint submission - each field has a description (field guidance) and value (user answer)

build_attempt
integer
default:1

Build attempt number (1-2). Validation runs only on attempt 1; attempt 2 skips re-validation.

Required range: 1 <= x <= 2
pipeline
enum<string>
default:cascaded

Engine for the generated agent. "s2s" builds the realtime pipeline on the same single-prompt agent; anything else builds the cascaded pipeline.

Available options:
cascaded,
s2s
target_shape
enum<string>
default:spa

Kind of agent to build. "cfa" writes a conversation-flow document (a step graph), "ivr" writes a touch-tone menu; anything else builds a single-prompt agent.

Available options:
spa,
cfa,
ivr

Response

Builder run completed or needs more input

success
enum<boolean>
required
Available options:
true
error
enum<boolean>
required
Available options:
false
statusCode
integer
required
Example:

201

message
string
required
Example:

"Success"

data
object
required
timestamp
string<date-time>
required