Upsert runtime database document

PUT/v1/servers/{serverId}/runtime/database/collections/{collectionId}/documents/{documentId}

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
NameLocationTypeRequiredDescription
serverIdpathstringYesResource ID
collectionIdpathstringYesCollection ID
documentIdpathstringYesDocument ID
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
dataobjectYes

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Runtime database document updatedapplication/json
FieldTypeRequiredDescription
serverIdstringNoResource ID.
databaseIdstringNoDatabase ID.
collectionIdstringNoCollection ID.
documentobjectNo
document.idstringNoUnique identifier.
document.dataobjectNo
document.createdAtstringNoISO 8601 timestamp.
document.updatedAtstringNoISO 8601 timestamp.
201Runtime database document createdapplication/json
FieldTypeRequiredDescription
serverIdstringNoResource ID.
databaseIdstringNoDatabase ID.
collectionIdstringNoCollection ID.
documentobjectNo
document.idstringNoUnique identifier.
document.dataobjectNo
document.createdAtstringNoISO 8601 timestamp.
document.updatedAtstringNoISO 8601 timestamp.
Upsert runtime database document
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow