Skip to main content
List members’ requests for more usage, read one request, and decline a request that is still waiting. There is no webhook. Poll the list. To approve a request, raise that member’s plan to Business Max or raise their extra usage limit, and pass usageRequestId on that write. See Set Included User Plan and Set User Extra Usage Limit. The calls use the workspace API key’s BILLING_API scope. The decline runs as the key’s service account owner.
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 or name
The list response is { "usageRequests": [ ... ] } and includes nextCursor until the last page. Reading one request returns the request object. A request outside this workspace returns 404 with code NOT_FOUND.
email and name are included only when the key also has USER_MANAGEMENT_API. Without that scope, those fields are omitted. name may be null when it is included. resolution is increased_limit, upgraded_plan, dismissed, or null while the request is pending. resolvedAt and resolvedByUserId are null while it is pending. resolvedByUserId is the admin or service account that answered the request.
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.