---
title: "Dismiss a usage request"
method: POST
path: "/billing/v1/ai-models-included/usage-requests/{requestId}/dismiss"
tags: ["Usage requests"]
---

# Dismiss a usage request

`POST /billing/v1/ai-models-included/usage-requests/{requestId}/dismiss`

## Request

- Base URL: `https://api.langdock.com`
- URL: `https://api.langdock.com/billing/v1/ai-models-included/usage-requests/{requestId}/dismiss`
- Auth: HTTP bearer

Declines a pending request as the key's service account. To approve, raise the member's limit or plan with the user PUT endpoints instead.

## Response `200`

The dismissed request.

- UsageRequest
  - `id` string, uuid, required
  - `userId` string, uuid, required
  - `email` string, email: Present only when the key also has the USER_MANAGEMENT_API scope.
  - `name` string, nullable: Present only when the key also has the USER_MANAGEMENT_API scope.
  - `status` 'pending' | 'resolved' | 'dismissed', required
  - `createdAt` string, date-time, required
  - `resolvedAt` string, date-time, nullable, required
  - `resolution` 'increased_limit' | 'upgraded_plan' | 'dismissed' | 'null', nullable, required: How the request was answered; null while pending.
  - `resolvedByUserId` string, uuid, nullable, required: Admin or service account that answered the request.

## Other responses

- `400`: Invalid body/query, unknown fields, empty PATCH, invalid limit, invalid bulk member IDs, or a cursor outside this workspace (INVALID_CURSOR).
- `401`: Missing or invalid authentication.
- `403`: Missing Billing scope, personal key, unavailable feature, missing active service-account Admin authority, or email filter without the USER_MANAGEMENT_API scope.
- `404`: Resource not in this workspace, inactive/non-human user, privacy-hidden agent, usage request not found for that member, or endpoint unavailable in this mode.
- `405`: Unsupported HTTP method.
- `409`: Workspace mode differs from the requested mode (BILLING_MODE_MISMATCH), the usage request is no longer pending (USAGE_REQUEST_NOT_PENDING, details.status holds its current status), or the write does not answer the named usage request (USAGE_REQUEST_NOT_ANSWERED).
- `429`: API rate limit exceeded.

## Changes

- **2026-11-03** `c62bf90b4013`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/langdock/apis/langdock-api/changes/billing/v1/ai-models-included/usage-requests/:requestId/dismiss/post.md)

---

[API](https://skmtc.dev/langdock/apis/langdock-api.md) - [All operations](https://skmtc.dev/langdock/apis/langdock-api/llms.txt) - [OpenAPI document](https://skmtc.dev/langdock/apis/langdock-api/revisions/c62bf90b4013?raw)