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 or extra usage budget and pass usageRequestId on that write. See Billing Users. The calls use the workspace API key’s BILLING_API scope. The decline runs as the key’s service account owner.

Base URL

Dedicated deploymentsReplace api.langdock.com with <your-deployment-url>/api/public in all requests.

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

Decline a request

POST /usage-requests/{requestId}/dismiss takes no body. The response is the request with status dismissed and resolution dismissed. A request that is no longer pending returns 409 with code USAGE_REQUEST_NOT_PENDING. The current status is in details.status. Nothing changes. A decline and a named plan or budget write for the same request cannot both succeed. The call that loses returns 409 and changes nothing.
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.