Skip to main content
Neon Postgres Docs
current

Search documentation

Type to search this documentation.

On this pageOverview

Retrieve current user details

Retrieves information about the currently authenticated Neon user,

GET /users/me

Retrieves information about the currently authenticated Neon user, including account identifiers, plan details, and linked auth accounts.

Markdown for AI context

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

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

Also available in

Bash
neon me

Tool: list_projects

List Neon projects in your account. Do not use for projects shared with you (use list_shared_projects instead). Supports optional search (filter by name or ID) and limit (default 10) parameters.

  • cursor (string, optional) Specify the cursor value from the previous response to retrieve the next batch of projects.
  • limit (number, optional, default: 10) Specify a value from 1 to 400 to limit number of projects in the response.
  • search (string, optional) Search by project name or id. You can specify partial name or id values to filter results.
  • org_id (string, optional) Search for projects by org_id.

Console path: Account settings → Profile

200

Returned information about the current user

Depth

"active_seconds_limit": (integer),reqint64

"email": (string),reqemail≥1 chars, ≤256 chars

"id": (string),req

"image": (string),req

"login": (string),reqdeprecated

"name": (string),req

"last_name": (string),req

"projects_limit": (integer),reqint64

"branches_limit": (integer),reqint64

"max_autoscaling_limit": (number),reqdouble

"plan": (string),req

"compute_seconds_limit": (integer),int64

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.

Suggest an edit

Propose a replacement for this page. The site team reviews it before applying any changes.

Export
Documentation menu