V1 API reference

Base URL

https://api.zelinqa.ai

Every application route uses HTTPS and an API key, except GET /v1/health.

Session runtime

Method	Route	Purpose
`POST`	`/v1/sessions`	Create a conversation.
`POST`	`/v1/sessions/{session_id}/next`	Apply the previous turn and obtain the next decision.
`POST`	`/v1/sessions/{session_id}/events`	Add context or data without selecting a question.
`GET`	`/v1/sessions/{session_id}`	Read and resume public state.
`POST`	`/v1/sessions/{session_id}/feedback`	Record the business outcome.

Configuration

Method	Route	Primary scope
`GET`	`/v1/configuration`	`configuration:read`
`GET`	`/v1/configuration/questions`	`configuration:read`
`GET`	`/v1/configuration/audit`	`configuration:publish`
`POST`	`/v1/configuration/changes`	`configuration:write`
`POST`	`/v1/configuration/publish`	`configuration:publish`
`GET`	`/v1/configuration/compilations/{compilation_id}`	`configuration:read`

Mintlify generates each interactive endpoint page from the engine’s V1 OpenAPI contract. The contract, not this prose, is authoritative for fields, types, and HTTP status codes.

Authentication and concurrency

Understand scopes, Idempotency-Key, and state_version.

Errors

Distinguish business errors from gateway denials and choose a recovery strategy.

Read a decision

Understand warnings, degraded operation, and hard-stop reasons.

The /v1/next-questions and /v1/sessions/{session_id}/conversion routes are deprecated. Use the session routes above for new integrations.

API guides

Sessions

Configuration

Service

V1 API reference

Base URL

Session runtime

Configuration

Authentication and concurrency

Errors

Read a decision

​Base URL

​Session runtime

​Configuration

Authentication and concurrency

Errors

Read a decision

Base URL

Session runtime

Configuration