Export user usage data
Usage Export API
Export User Usage
API endpoint to export user activity data including message counts and usage patterns (subject to privacy settings)
POST
Export user usage data
This endpoint exports user activity data including message counts, usage patterns, and feature utilization. The available data depends on your workspace privacy settings.
For details on prerequisites and rate 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.
Privacy Considerations
The user export data is subject to workspace privacy settings, user-identifying data may be excluded due to privacy settings. As a consequence of this some data may be anonymized based on workspace configuration.Data Included
By default, the user export returns one row per user for the selected period.| Column | Description |
|---|---|
period_start | Start date of the report |
period_end | End date of the report |
org_id | ID of the workspace |
user_id | ID of the user |
name | Name of the user |
email | Email of the user |
role | User role |
joined_at | Date the user joined the workspace |
department | User department |
company_name | User company name |
license_type | Current license tier |
payg_limit_current | Current extra-usage limit |
payg_consumption_in_period | Extra-usage consumption in the selected period |
payg_utilization_pct_current | payg_consumption_in_period / payg_limit_current |
messages_total | Total messages sent by the user |
messages_total_rank | Rank by total messages |
messages_chat | Messages sent in regular chats |
messages_chat_rank | Rank by chat messages |
messages_assistants | Messages sent to agents |
messages_assistants_rank | Rank by agent messages |
assistants_messaged | Number of distinct agents messaged |
assistants_to_messages | JSON mapping agent ID to message count |
messages_projects | Messages sent to projects |
messages_projects_rank | Rank by project messages |
projects_messaged | Number of distinct projects messaged |
projects_to_messages | JSON mapping project ID to message count |
model_to_messages_total | JSON mapping model name to message count |
action_messages | Messages generated by actions |
action_messaged | Number of distinct actions triggered |
action_to_messages | JSON mapping action name to message count |
Additional Columns for BYOK Workspaces
| Column | Description |
|---|---|
total_input_tokens | Total input tokens consumed by the user |
total_output_tokens | Total output tokens generated for the user |
cached_prompt_tokens | Cache-read input tokens |
cache_creation_tokens | Cache-write input tokens |
no_cache_tokens | Input tokens that were not served from cache |
total_cost_usd | Estimated provider cost in USD |
Because BYOK workspaces supply their own model keys, Langdock can provide token consumption and costs directly. This is not possible when obtaining your models directly through Langdock.
Grouped Export
Usegroup_by=model to return one row per user and model.Authorizations
API key as Bearer token. Format "Bearer YOUR_API_KEY"
Body
application/json