Skip to main content
POST
/
export
/
assistants
Export assistant usage data
curl --request POST \
  --url https://api.langdock.com/export/assistants \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "from": {
    "date": "2024-01-01T00:00:00.000Z",
    "timezone": "UTC"
  },
  "to": {
    "date": "2024-01-31T23:59:59.999Z",
    "timezone": "UTC"
  }
}
'
{
  "success": true,
  "data": {
    "filePath": "assistants-usage/workspace-id/assistants-usage-2024-01-01-2024-01-31-abc12345.csv",
    "downloadUrl": "https://storage.example.com/signed-url",
    "dataType": "assistants",
    "recordCount": 1250,
    "dateRange": {
      "from": "2024-01-01T00:00:00.000Z",
      "to": "2024-01-31T23:59:59.999Z"
    }
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.langdock.com/llms.txt

Use this file to discover all available pages before exploring further.

This endpoint exports agent usage data including message counts per agent, active user counts, and usage trends over time.
Using a dedicated deployment?Replace api.langdock.com with <your-deployment>/api/public in all requests.

​
Data Included

The agent export contains:
  • Number of messages per agent
  • Active users per agent
  • Prompt token consumption per agent (BYOK workspaces only)
  • Completion token consumption per agent (BYOK workspaces only)
  • Cached token usage per agent (BYOK workspaces only)
Because BYOK workspaces supply their own model keys, Langdock can provide token consumption data directly. This is not possible when obtaining your models directly through Langdock.
For details on prerequisites, rate limits, and export size limits, please refer to the main Usage Export API documentation.
Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, please see our guide on API Key Best Practices.

Authorizations

​
Authorization
string
header
required

API key as Bearer token. Format "Bearer YOUR_API_KEY"

Body

application/json

Request body for usage export endpoints

​
from
object
required

Start date and timezone for the export

​
to
object
required

End date and timezone for the export

Response

Export successful

Successful response from usage export endpoints

​
success
boolean
required

Indicates if the export was successful

Example:

true

​
data
object
required

Export data information