Skip to main content
POST
Continue a prior response

Authorizations

Authorization
string
header
required

Bearer token authentication. Supports two token types:

  • JWT Access Token — obtained via POST /v1/auth/login
  • Personal Access Token (PAT) — created via POST /v1/api-tokens, format: cmnd_<tokenId>.<secret>

Path Parameters

resp_id
string
required

Id of the prior response to continue

Body

application/json
model
string
required
Example:

"gpt-4o-mini"

input
required

The prompt or conversation input. Accepts either a plain string or an array of typed content parts (text, input_image, input_file, …) per the Responses API shape supported by the backend model.

instructions
string

Optional system-style instructions applied to the response.

max_output_tokens
integer
Required range: x >= 1
temperature
number
Required range: 0 <= x <= 2
top_p
number
Required range: 0 <= x <= 1
stream
boolean
default:false
previous_response_id
string

Id of a prior response to continue. Callers can also POST to /v1/responses/{resp_id}/continue.

Response

Successful response

id
string
Example:

"resp_abc123"

object
string
Example:

"response"

created
integer
model
string
output

Model output. Shape depends on the backend and on whether stream was requested; for non-streaming calls this is typically an array of content parts (or a compact output_text string alongside them).

usage
object