# Set organization spending limit

`PUT /organizations/{org_id}/billing/spending_limitbeta`

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.

[Markdown for AI context](/guides/apis-sdks-reference-api-organizations-set-organization-spending-limit)

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

Also available in

::::tabs
:::tab{title="SDK"}
```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
  }
});
```
:::

:::tab{title="Console"}
Console path: Organization → Billing → Spending limit
:::
::::

## Parameters

Organization

`org_id`

string

The Neon organization ID

## Request body

**1 required** Required: `spending_limit_cents`.

Spending limit cents

`spending_limit_cents`

integer

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.

min: 1

## Response

200

The updated spending limit value.

Depth

"spending\_limit\_cents": (integer),reqint64

## Errors

default

General error

This endpoint can return the standard Neon API error response.

Response fields

- `message` Required. Human-readable error message.
- `code` Required. Machine-readable error code.
- `request_id` Optional. Request identifier for debugging. You can provide one with the `X-Request-ID` header.

Retry guidance

If no response is returned, the request may still have reached the server. This is why retry safety depends on the method and status code.

Idempotent methods (`GET`, `HEAD`, `OPTIONS`) are generally safe to retry after a network error or timeout. Non-idempotent methods (`POST`, `PATCH`, `DELETE`, `PUT`) can change state, so avoid automatic retries unless your workflow can tolerate duplicate effects.

Responses with `423 Locked` or `503 Service Unavailable` are safe to retry. `423 Locked` means the resource is temporarily locked, usually because another operation is in progress.

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