Neon · Schema

Neon Operation

A Neon operation tracks the progress of an action performed on a project resource such as creating a branch, starting a compute endpoint, or applying configuration changes.

DatabasesServerlessPostgresInfrastructureAuthenticationEdge

Properties

Name Type Description
id string The unique operation identifier
project_id string The project ID this operation belongs to
branch_id string The branch ID associated with this operation, if applicable
endpoint_id string The endpoint ID associated with this operation, if applicable
action string The type of action being performed by this operation
status string The current status of the operation
failures_count integer Number of times the operation has failed and been retried
error string Error message if the operation failed
created_at string Timestamp when the operation was created
updated_at string Timestamp when the operation status was last updated
View JSON Schema on GitHub

JSON Schema

neon-operation-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://neon.com/schemas/neon/operation.json",
  "title": "Neon Operation",
  "description": "A Neon operation tracks the progress of an action performed on a project resource such as creating a branch, starting a compute endpoint, or applying configuration changes.",
  "type": "object",
  "required": ["id", "project_id", "action", "status"],
  "properties": {
    "id": {
      "type": "string",
      "description": "The unique operation identifier"
    },
    "project_id": {
      "type": "string",
      "description": "The project ID this operation belongs to"
    },
    "branch_id": {
      "type": "string",
      "description": "The branch ID associated with this operation, if applicable"
    },
    "endpoint_id": {
      "type": "string",
      "description": "The endpoint ID associated with this operation, if applicable"
    },
    "action": {
      "type": "string",
      "description": "The type of action being performed by this operation",
      "enum": [
        "create_compute",
        "create_timeline",
        "start_compute",
        "suspend_compute",
        "apply_config",
        "check_availability",
        "delete_timeline",
        "create_branch",
        "tenant_ignore",
        "tenant_attach",
        "tenant_detach",
        "replace_safekeeper"
      ]
    },
    "status": {
      "type": "string",
      "description": "The current status of the operation",
      "enum": [
        "scheduling",
        "running",
        "finished",
        "failed",
        "cancelling",
        "cancelled",
        "skipped"
      ]
    },
    "failures_count": {
      "type": "integer",
      "description": "Number of times the operation has failed and been retried",
      "minimum": 0
    },
    "error": {
      "type": "string",
      "description": "Error message if the operation failed"
    },
    "created_at": {
      "type": "string",
      "format": "date-time",
      "description": "Timestamp when the operation was created"
    },
    "updated_at": {
      "type": "string",
      "format": "date-time",
      "description": "Timestamp when the operation status was last updated"
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/neon-operation"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.