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

# Decline Included Usage Request

> Decline a member's usage request that is still waiting 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}/dismiss
```

## 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 limit write for the same request cannot both succeed. The call that loses returns `409` and changes nothing.

> [!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.