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
plan is business or business_max. email is an exact address and ignores case. limit defaults to 50 and cannot exceed 250. Pass cursor from nextCursor. To look a member up by email, call GET /users?email=jane%40example.com with a key that also has the User Management scope, then update by the returned id. The list response is { "users": [ ... ] } and includes nextCursor until the last page. Each member is the object described on Get Included User.
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.