Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Neon Roles API

Manage Postgres roles within a branch. Roles control database access and permissions.

Neon Roles API is one of 13 APIs that Neon publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Roles. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 3 paths, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version 2.0.

Requests are made against a single base URL, https://console.neon.tech/api/v2.

5 operations 3 paths 3 schemas 1 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0
Base URL
https://console.neon.tech/api/v2
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Neon Roles API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API Key) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Neon API keys are used to authenticate requests. Include the API key in the Authorization header as a Bearer token.

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Roles 5

Manage Postgres roles within a branch. Roles control database access and permissions.

GET
/projects/{project_id}/branches/{branch_id}/roles
List roles
listProjectBranchRoles 2 params → 200401404
POST
/projects/{project_id}/branches/{branch_id}/roles
Create a role
createProjectBranchRole 2 params body → 201400401404
GET
/projects/{project_id}/branches/{branch_id}/roles/{role_name}
Retrieve role details
getProjectBranchRole 3 params → 200401404
DELETE
/projects/{project_id}/branches/{branch_id}/roles/{role_name}
Delete a role
deleteProjectBranchRole 3 params → 200401404
POST
/projects/{project_id}/branches/{branch_id}/roles/{role_name}/reset_password
Reset role password
resetProjectBranchRolePassword 3 params → 200401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Operation (9 properties), Role (6 properties), RoleCreateRequest (1 property). Each schema is shown below with its type and property counts.

RoleCreateRequest
object
Request body for creating a new role
1 property 1 required
Role
object
A Postgres role within a branch
6 properties
Operation
object
An operation tracks the progress of an action performed on a project resource such as creating a branch, starting an endpoint, or updating a database.
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

neon-roles-api-openapi.yml Raw ↑

Other APIs Neon publishes across the network.

Neon Data API
Neon Serverless Driver
Neon Auth
Neon API Keys API
Neon Auth API
Neon Branches API
Neon Consumption API
Neon Data API API
Neon Databases API
Neon Endpoints API
Neon Operations API
Neon Projects API