Skip to main content
List active human members, change a plan, and set the extra usage limit. Amounts are euros. The calls use the workspace API key’s BILLING_API scope. Writes run as the key’s service account owner. This API does not invite or deactivate members. Use the User Management API for that.
Call these routes when GET /billing/v1/mode returns ai-models-included. Dedicated deployments always return bring-your-own-keys, including when Langdock manages the model keys. The other mode returns 409 with code BILLING_MODE_MISMATCH.

​
Base URL

​
Prerequisites

  • API key with the BILLING_API scope
  • The key owner is a service account that has not been deleted and has an active Admin membership
  • USER_MANAGEMENT_API on the same key when you need email, name, or an email filter
A member object includes email and name only when the key also has USER_MANAGEMENT_API. Without that scope, those fields are omitted. name may be null when it is included.
plan is business (Business) or business_max (Business Max). configured is the limit stored on the member: inherit, limited, or unlimited. inherit means the member has no personal cap. An explicit limited or unlimited value overrides the plan and every group. effective is the limit that applies. With inherit, the higher of the plan default and the member’s group limits applies. An unlimited value wins over a limited one. When the amounts match, a group wins over the plan. When two groups set the same amount, the source is the group whose name comes first. source.type is plan, group, user, or workspace. A group source also includes groupId and groupName. source is user when the member has an explicit cap. An unlimited group does not override that cap. source is workspace and the effective amount is zero when extra usage is turned off for the workspace. An unlimited member or group limit does not override that switch or the workspace extra usage cap. extraUsagePeriodSpend is extra usage in the current period. It is null when the workspace hides per user spend. A user who is not an active human member returns 404.
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.