# List compute endpoints

`GET /projects/{project_id}/endpoints`

Retrieves a list of compute endpoints for the specified project. A compute endpoint is a Neon compute instance. For information about compute endpoints, see [Manage computes](/guides/manage-operate-manage-computes).

[Markdown for AI context](/guides/apis-sdks-reference-api-endpoints-list-project-endpoints)

```bash title="REST API - curl"
curl "https://console.neon.tech/api/v2/projects/$PROJECT_ID/endpoints" \
  -H "Authorization: Bearer $NEON_API_KEY"
```

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

Also available in

::::tabs
:::tab{title="SDK"}
```typescript
import { createNeonClient, raw } from '@neon/sdk';

const neon = createNeonClient({ apiKey: process.env.NEON_API_KEY });
const { data } = await raw.listProjectEndpoints({
  client: neon.client,
  path: {
    project_id: process.env.PROJECT_ID
  }
});
```
:::

:::tab{title="MCP"}
Tool: `list_branch_computes`

List compute endpoints for a project or branch. Do not use when you need a connection string: use `get_connection_string`, which requires write access and is unavailable in read-only mode.

- `projectId` (string, optional)
  The ID of the project. If not provided, the only available project will be used.
- `branchId` (string, optional)
  The ID of the branch. If provided, endpoints for this specific branch will be listed.
:::

:::tab{title="Console"}
Console path: Projects → Branches → Computes
:::
::::

## Parameters

Project ID

`project_id`

string

The Neon project ID

## Response

200

Returned a list of endpoints for the specified project

::::tabs
:::tab{title="schema"}
Depth
:::

:::tab{title="example"}
:::
::::

## 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.

## Related pages

- [Create compute endpoint](./apis-sdks-reference-api-endpoints-create-project-endpoint.md)
- [Delete compute endpoint](./apis-sdks-reference-api-endpoints-delete-project-endpoint.md)
- [Restart compute endpoint](./apis-sdks-reference-api-endpoints-restart-project-endpoint.md)
- [Retrieve compute endpoint details](./apis-sdks-reference-api-endpoints-get-project-endpoint.md)
- [Start compute endpoint](./apis-sdks-reference-api-endpoints-start-project-endpoint.md)
- [Suspend compute endpoint](./apis-sdks-reference-api-endpoints-suspend-project-endpoint.md)
- [Update compute endpoint](./apis-sdks-reference-api-endpoints-update-project-endpoint.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.