Skip to main content
POST
/
export
/
models
Export model usage data
curl --request POST \
  --url https://api.langdock.com/export/models \
  --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": "agents-usage/workspace-id/agents-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"
    }
  }
}
⚠️ Using our API via a dedicated deployment? Just replace api.langdock.com with your deployment’s base URL: <deployment-url>/api/public
This endpoint exports AI model usage data including request counts and token consumption per model.

​
Data Included

The model export always contains:
  • period_start, period_end — time range
  • org_id — workspace identifier
  • name — model name
  • requests — number of requests
BYOK Required for Token Data: Token columns (sum_prompt_tokens, sum_completion_tokens, sum_cached_prompt_tokens, sum_cache_creation_tokens) are only included when Bring Your Own Keys (BYOK) is active in your workspace. With Langdock-managed keys, only the basic columns above are exported.

​
Usage Analysis (BYOK Only)

With BYOK enabled, the token data allows you to:
  • Calculate costs using your provider’s pricing
  • Identify which models consume the most tokens
  • Track usage trends over time
  • Optimize model selection for different use cases
Additional Information: 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