Skip to content
Proud to collaborate with Microsoft for Startups

neon.data_apis.create ​

Enable the Neon Data API on a branch database

Enable (create) the Neon Data API for a database on a branch.

Issues POST /projects/{neon_project_id}/branches/{neon_branch_id}/data-api/{db_name}. The Data API exposes a PostgREST-compatible HTTP interface over Postgres.

Inputs:

  • neon_project_id: Neon project ID (required).
  • neon_branch_id: Neon branch ID (required).
  • db_name: Database name to expose (required).
  • auth_provider: neon_auth | external (optional).
  • jwks_url: JWKS URL when auth_provider is external (optional).
  • provider_name: Display name for an external provider (optional).
  • jwt_audience: Expected JWT aud claim (optional).
  • add_default_grants: Grant public-schema table perms to authenticated (optional).
  • skip_auth_schema: Skip creating auth schema / RLS helpers (optional).
  • settings: Data API settings object (optional; see Neon docs).

Outputs (terminal state_data):

  • data_api_url: str — REST base URL for the enabled Data API
  • provider_metadata: dict — raw Neon response body

Error policy:

  • 4xx → WorkflowNotRetryableError (already enabled, invalid config, etc.).
  • 5xx / timeouts → propagate so the engine retries.

Plugin required: context.get_plugin("neon") must expose .api_token.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-neon
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
connection_uuiduuidYes—Cloud connection holding the Neon credential
neon_project_idstringYes—Neon project ID
neon_branch_idstringYes—Neon branch ID
db_namestringYes—Database name to expose via the Data API
auth_providerstringNo—neon_auth
jwks_urlstringNo—JWKS URL for external JWT provider
provider_namestringNo—Display name for the external provider
jwt_audiencestringNo—Expected JWT aud claim
add_default_grantsbooleanNo—Grant public schema table perms to authenticated
skip_auth_schemabooleanNo—Skip creating the auth schema and RLS helpers
settingsjsonNo—Data API settings object (schemas, CORS, etc.)

Output Schema ​

FieldTypeRequiredDefaultDescription
connection_uuiduuidNo——
neon_project_idstringNo——
neon_branch_idstringNo——
db_namestringNo——
auth_providerstringNo——
jwks_urlstringNo——
provider_namestringNo——
jwt_audiencestringNo——
add_default_grantsbooleanNo——
skip_auth_schemabooleanNo——
settingsjsonNo——
data_api_urlstringNo—PostgREST base URL for the Data API
provider_metadatajsonNo——
failure_reasonstringNo——
failure_typestringNo——
failed_actionstringNo——
failed_at_statestringNo——
failed_stepstringNo——
failed_layerstringNo——
errorstringNo——
error_typestringNo——

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—execute—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
pendingexecutecompleted—
* (any state)failfailed—

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "neon.data_apis.create",
  "initial_data": {
    "connection_uuid": "value",
    "neon_project_id": "value",
    "neon_branch_id": "value",
    "db_name": "value"
  }
}