Neo4j Transactions API
Manage explicit transactions with full control over the transaction lifecycle including open, run, commit, and rollback operations.
Neo4j Transactions API is one of 12 APIs that Neo4j publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Transactions. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 4 operations across 3 paths, and defines 9 schemas. It is described by OpenAPI 3.1.0, at version 1.0.
Requests are made against a single base URL, https://api.neo4j.io/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Neo4j Transactions API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
By default, every request must be authenticated.
bearerAuth— OAuth2 bearer token obtained from the /oauth/token endpoint using client credentials. Tokens expire after one hour.
Paths & Operations 4
Across 3 paths, the API surfaces 4 operations — 1 DELETE, 3 POST. Each is listed below with its method, path, parameters, and response codes.
Manage explicit transactions with full control over the transaction lifecycle including open, run, commit, and rollback operations.
Schemas 9
The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are QueryStatistics (12 properties), GraphRelationship (5 properties), TransactionResponse (4 properties), CypherStatement (4 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Neo4j 11
Other APIs Neo4j publishes across the network.