Skip to main content
Conversation exports include the arguments sent to a tool and the value it returned when you set both include_message_content=true and include_action_results=true.

Endpoints

Send both parameters on any of these requests:
List responses include next_cursor. Pass that value as cursor to read the next page. limit defaults to 50. The maximum is 50. GET /api/compliance/{workspace_id}/messages returns usage and cost rows. Tool parameters and outputs are on the conversation endpoints above.

Base URL

Dedicated deploymentsReplace app.langdock.com with your deployment URL. Keep the path /api/compliance/....

Before You Start

  • Create an API key with the Compliance API scope in Settings > API.
  • Send the key as Authorization: Bearer YOUR_API_KEY.
On Cloud, these requests return 404 until the Compliance API is turned on for your workspace. The Compliance API scope stays hidden until then. Dedicated deployments serve the API unless that deployment turns it off.

Parameters

Pass true or false as strings. Any other value returns 400. With only include_message_content=true, tool messages still appear. content is the action name, and action_name, action_input, action_output, and is_error are omitted. With only include_action_results=true, the response omits messages.

Tool fields

With both parameters set to true, a tool message includes: User and assistant messages include message_id, role, content, and created_at.

Example