List supported regions
Lists supported Neon regions.
GET /regions
Lists supported Neon regions.
Note: Not all regions are available to all organizations. Pass the org_id parameter to get an accurate list of regions available to your organization.
curl "https://console.neon.tech/api/v2/regions" \
-H "Authorization: Bearer $NEON_API_KEY"Every field below is optional. An empty body works too.
import { createNeonClient, raw } from '@neon/sdk';
const neon = createNeonClient({ apiKey: process.env.NEON_API_KEY });
const { data } = await raw.getActiveRegions({
client: neon.client
});Parameters
Section titled “Parameters”Organization
org_id
string
Organization ID. When provided, returns only regions available to this organization. Recommended for accurate region availability.
Response
Section titled “Response”200
The list of active regions
Depth
Errors
Section titled “Errors”default
General error
This endpoint can return the standard Neon API error response.
Response fields
messageRequired. Human-readable error message.codeRequired. Machine-readable error code.request_idOptional. Request identifier for debugging. You can provide one with theX-Request-IDheader.
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.