Skip to main content
Read groups and set an extra usage limit for each member of a group. The limit is not a shared pool. 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 add or remove group members.
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

​
Set the extra usage limit

PUT /groups/{groupId}/extra-usage-limit takes the limit directly.
{ "type": "unlimited" } removes the numeric cap. A limited amount may be zero. This value does not accept inherit or none. For each member who inherits, the extra usage limit is the higher of the plan default and this group limit. An explicit member limit still wins. An unlimited group limit does not remove the workspace cap or override extra usage turned off. See Get Included User for how the effective source is chosen. SCIM-managed groups accept this change. Membership stays with the identity provider. The response is the group object.
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.