List organizations for the current user

Retrieves the organizations that the currently authenticated user belongs to.

GET /users/me/organizations

Retrieves the organizations that the currently authenticated user belongs to.

When called with an organization- or project-scoped API key (which is not tied to a user), this returns the single organization that owns the key.

Markdown for AI context

REST API - curl

curl "https://console.neon.tech/api/v2/users/me/organizations" \
  -H "Authorization: Bearer $NEON_API_KEY"

Every field below is optional. An empty body works too.

Also available in

Bash

neon orgs list

Tool: list_organizations

List all organizations the current user belongs to. Supports optional search parameter to filter by name or ID.

search (string, optional) Search organizations by name or ID. You can specify partial name or ID values to filter results.

Console path: Account settings → Profile

Response

200

Returned information about the current user organizations

Depth

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.