# Set organization spending limit

> API Reference / Organizations / Set organization spending limit

## PUT /organizations//billing/spending\_limit

Sets the monthly spending limit for the specified organization.
To remove a previously configured limit, send a DELETE request to this endpoint.
When a limit is configured, email notifications are sent at 80% and 100% of the limit.
Computes are not suspended when the limit is reached.
Available to organization admins on Launch and Scale plans only.

### Parameters

- `org_id` (string, path, required)
  The Neon organization ID

### Request body

- `spending_limit_cents` (integer, required, format: int64)
  Monthly spending cap in cents. Must be positive. To remove a
  previously configured limit, send a DELETE request to the
  spending\_limit endpoint — `0` and `null` are rejected here.
  The cap is alert-only: notifications fire at 80% and 100%, but
  computes are not suspended. Setting a cap below the period's
  already-accrued spend is permitted and will trigger the
  over-limit notification on the next worker run.

### Response (200)

- `spending_limit_cents` (integer, optional, format: int64)
  Monthly spending cap in cents. `null` indicates that no limit
  is currently configured.

### Code examples

```bash
curl "https://console.neon.tech/api/v2/organizations/$ORG_ID/billing/spending_limit" \
  -X PUT \
  -H "Authorization: Bearer $NEON_API_KEY"
```

```typescript
import { createNeonClient, raw } from '@neon/sdk';

const neon = createNeonClient({ apiKey: process.env.NEON_API_KEY });
const { data } = await raw.setOrganizationSpendingLimit({
  client: neon.client,
  path: {
    org_id: process.env.ORG_ID
  }
});
```

### Console

Console path: Organization → Billing → Spending limit

### Errors

**default**
General Error.

The request may or may not be safe to retry, depending on the HTTP method, response status code,
and whether a response was received.

- If no response is returned from the API, a network error or timeout likely occurred.
- In some cases, the request may have reached the server and been successfully processed, but the response failed to reach the client. As a result, retrying non-idempotent requests can lead to unintended results.

The following HTTP methods are considered non-idempotent: `POST`, `PATCH`, `DELETE`, and `PUT`. Retrying these methods is generally **not safe**.
The following methods are considered idempotent: `GET`, `HEAD`, and `OPTIONS`. Retrying these methods is **safe** in the event of a network error or timeout.

Any request that returns a `503 Service Unavailable` response is always safe to retry.

Any request that returns a `423 Locked` response is safe to retry. `423 Locked` indicates that the resource is temporarily locked, for example, due to another operation in progress.

- `request_id` (string, optional)
  Unique identifier for the request, useful for debugging.
  You can set this value manually by including an `X-Request-ID` header in the request. If not provided, the value will be generated automatically.

- `code` (string, required)
  Machine-readable code classifying the error type. See `message` for a human-readable explanation.
  Default: \`\`

- `message` (string, required)
  Error message

## Related pages

- [Assign or update VPC endpoint](./apis-sdks-reference-api-organizations-assign-organization-vpc-endpoint.md)
- [Create organization API key](./apis-sdks-reference-api-organizations-create-org-api-key.md)
- [Create organization invitations](./apis-sdks-reference-api-organizations-create-organization-invitations.md)
- [Delete VPC endpoint](./apis-sdks-reference-api-organizations-delete-organization-vpc-endpoint.md)
- [List organization API keys](./apis-sdks-reference-api-organizations-list-org-api-keys.md)
- [List organization invitations](./apis-sdks-reference-api-organizations-get-organization-invitations.md)
- [List organization members](./apis-sdks-reference-api-organizations-get-organization-members.md)
- [List VPC endpoints](./apis-sdks-reference-api-organizations-list-organization-vpc-endpoints.md)
- [List VPC endpoints across all regions](./apis-sdks-reference-api-organizations-list-organization-vpc-endpoints-all-regions.md)
- [Remove organization member](./apis-sdks-reference-api-organizations-remove-organization-member.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.