> ## Documentation Index
> Fetch the complete documentation index at: https://docs.langdock.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Included Usage Request

> Read one member's request for more usage on an AI models included workspace

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](https://docs.langdock.com/en/developer/billing-api/set-included-user-plan.md) and [Set User Extra Usage Limit](https://docs.langdock.com/en/developer/billing-api/set-user-extra-usage-limit.md).

The calls use the workspace API key's `BILLING_API` scope. The decline runs as the key's service account owner.

> [!NOTE]
>
> 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

```
https://api.langdock.com/billing/v1/ai-models-included/usage-requests/{requestId}
```

## 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`.

```json theme={null}
{
  "id": "44444444-4444-4444-8444-444444444444",
  "userId": "11111111-1111-4111-8111-111111111111",
  "email": "ada@example.com",
  "name": "Ada Lovelace",
  "status": "resolved",
  "createdAt": "2026-10-01T08:30:00.000Z",
  "resolvedAt": "2026-10-01T09:05:00.000Z",
  "resolution": "increased_limit",
  "resolvedByUserId": "55555555-5555-4555-8555-555555555555"
}
```

`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.

> [!NOTE]
>
> 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](https://docs.langdock.com/en/admin/ai-adoption-and-rollout/best-practices/api-key-best-practices.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.