Atomically commit runtime database documents
POST
/v1/servers/{serverId}/runtime/database/commitCommit one to 500 document writes against the database bound to this runtime. Every write requires an explicit existence or update-time precondition, and the complete batch succeeds or fails as one transaction.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| serverId | path | string | Yes | Resource ID |
Query parameters
None.
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| writes | object[] | Yes | — |
| writes[].operation | upsert | Yes | — |
| writes[].collectionId | string | Yes | Collection ID. |
| writes[].documentId | string | Yes | Document ID. |
| writes[].data | object | Yes | — |
| writes[].precondition | object | Yes | — |
| writes[].precondition.exists | boolean | Yes | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Atomic database commit completedapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| serverId | string | No | Resource ID. |
| databaseId | string | No | Database ID. |
| commit | object | No | — |
| commit.commitTime | string | Yes | — |
| commit.writes | object[] | Yes | — |
| commit.writes[].operation | upsert | delete | Yes | — |
| commit.writes[].collectionId | string | Yes | Collection ID. |
| commit.writes[].documentId | string | Yes | Document ID. |
| commit.writes[].updatedAt | string | No | ISO 8601 timestamp. |
409One or more document preconditions failed; no writes were applied
None.
Atomically commit runtime database documents
Loading...
Response 200
Loading...