/projects/{project_id}/endpoints/{endpoint_id}/startStart compute endpoint
Starts a compute endpoint. The compute endpoint is ready to use after the last operation in the chain finishes successfully.
An endpoint_id has an ep- prefix.
For information about compute endpoints, see Manage computes.
Quick start
curl "https://console.neon.tech/api/v2/projects/$PROJECT_ID/endpoints/$ENDPOINT_ID/start" \
-X POST \
-H "Authorization: Bearer $NEON_API_KEY"Every field below is optional. An empty body works too.
import { createNeonClient, raw } from '@neon/sdk';
const neon = createNeonClient({ apiKey: process.env.NEON_API_KEY });
const { data } = await raw.startProjectEndpoint({
client: neon.client,
path: {
project_id: process.env.PROJECT_ID,
endpoint_id: process.env.ENDPOINT_ID
}
});Parameters
project_idThe Neon project ID
endpoint_idThe endpoint ID
Response
200Started the specified compute endpoint
Errors
General error
This endpoint can return the standard Neon API error response.
Response fields
messageRequired. Human-readable error message.codeRequired. Machine-readable error code.request_idOptional. Request identifier for debugging. You can provide one with theX-Request-IDheader.
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.