Add a follow-up message to an LRT job conversation

Learn more about add a follow-up message to an LRT job conversation.

Use the Add a follow-up message to an LRT job conversation to add a follow-up message to an LRT job conversation. This lets you continue a job's conversation instead of starting a new one.

HTTP method and endpoint

Use the following HTTP method and endpoint path to add a follow-up message to an LRT job conversation.

POST {TenantURL}/ai/agentflow/api/v202605/{tenant_id}/lrt/jobs/{job_id}/messages

The following table describes the endpoint path parameters.


Parameter	Type	Required	Description
`TenantURL`	String	Yes	The base URL for your tenant.
`job_id`	String	Yes	The unique identifier of the LRT job.
`tenant_id`	String	Yes	The tenant identifier.

Request headers

The following request headers must be included.


Header	Value	Required
`Authorization`	`<access_token>`	Yes

Request body

This operation does not require a request body.

Example request

Use the following example to see how a complete request is structured, with headers.

POST {TenantURL}/ai/agentflow/api/v202605/tenant-xyz/lrt/jobs/example-id/messages
Authorization: <access_token>

Response body

The following table describes the fields returned in the response body.


Parameter	Type	Description
`job_id`	String	The unique identifier of the LRT job.
`status`	String	The status of the job.
`next_run_at`	String	The date and time when the job is next queued to run.

Example response

The following example shows a response with successful response.

{
  "job_id": "0b4720e4-0b1c-41f7-9b53-0ebc907f45f8",
  "status": "active",
  "next_run_at": "2026-05-18T10:30:00+00:00"
}

Error codes and recommended actions

The following table lists the possible error responses returned by this API.


HTTP status	Description	Recommended action
`422 Unprocessable Entity`	Validation Error	Review the request parameters or body, correct the invalid values, and resend the request.

Unify and manage your data