Skip to main content
Neon Docs

Search documentation

Type to search this documentation.

List organizations for the current user

GET/users/me/organizationsList organizations for the current user

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.

Responses

200Returned information about the current user organizations application/json
objectOrganizationsResponse
organizationsarray of objectrequired

Organizations returned by the request. Each includes `id`, `name`, `handle`, and `plan`.

Show child attributes
Show array items
allow_hipaa_projectsboolean

If true, allow account to mark projects as HIPAA

created_atstring · date-timerequired

A timestamp indicting when the organization was created

handlestringrequired

URL-safe identifier for the organization, used in API paths. Distinct from the display name.

idstringrequired

The Neon organization ID. Use as the `org_id` path parameter in other endpoints.

pattern ^[a-z0-9-]{1,60}$

managed_bystringrequired

Organizations created via the Console or the API are managed by `console`. Organizations created by other methods can't be deleted via the Console or the API.

namestringrequired

Human-readable display name of the organization.

planstringrequired

Billing plan for the organization, for example `free`, `launch`, or `scale`.

require_mfaboolean

If true, all members must have MFA enabled to access this organization

updated_atstring · date-timerequired

A timestamp indicating when the organization was updated

Example response
{
  "organizations": [
    {
      "allow_hipaa_projects": true,
      "created_at": "2026-06-09T00:00:00Z",
      "handle": "string",
      "id": "string",
      "managed_by": "string",
      "name": "string",
      "plan": "string",
      "require_mfa": true,
      "updated_at": "2026-06-09T00:00:00Z"
    }
  ]
}
defaultGeneral 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. application/json
objectGeneralError
codestringrequired

default ""

messagestringrequired

Error message

request_idstring

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.

Example response
{
  "code": "",
  "message": "string",
  "request_id": "string"
}
Documentation menu