List shared projects

Retrieves a list of projects shared with your Neon account.

GET /projects/shared

Retrieves a list of projects shared with your Neon account. For more information, see Manage projects.

REST API - curl

curl "https://console.neon.tech/api/v2/projects/shared" \
  -H "Authorization: Bearer $NEON_API_KEY"

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

Also available in

Bash

neon projects list

Tool: list_shared_projects

List projects shared with the current user for collaboration. Do not use for projects you own (use list_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 shared projects.
limit (number, optional, default: 10) Specify a value from 1 to 400 to limit number of shared projects in the response.
search (string, optional) Search by project name or id. You can specify partial name or id values to filter results.

Console path: Organization → Projects

Parameters

Cursor

cursor

string

Specify the cursor value from the previous response to get the next batch of projects.

Limit

limit

integerdefault: 10

Specify a value from 1 to 400 to limit number of projects in the response.

search

string

Search query by name or id.

Timeout

timeout

integer

Specify an explicit timeout in milliseconds to limit response delay. After timing out, the incomplete list of project data fetched so far will be returned. Projects still being fetched when the timeout occurred are listed in the "unavailable" attribute of the response. If not specified, an implicit implementation defined timeout is chosen with the same behaviour as above

Response

200

Returned a list of shared projects for the Neon account

Depth

"unavailable_project_ids": (array),

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.