/projects/{project_id}/operationsList operations
Retrieves a list of operations for the specified Neon project.
The number of operations returned can be large.
To paginate the response, issue an initial request with a limit value.
Then, add the cursor value that was returned in the response to the next request.
Operations older than 6 months may be deleted from our systems.
If you need more history than that, you should store your own history.
Quick start
curl "https://console.neon.tech/api/v2/projects/$PROJECT_ID/operations" \
-H "Authorization: Bearer $NEON_API_KEY"Every field below is optional. An empty body works too.
neon operations listParameters
cursorSpecify the cursor value from the previous response to get the next batch of operations
limitSpecify a value from 1 to 1000 to limit number of operations in the response
project_idThe Neon project ID
Response
200Returned a list of operations
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.