Create runtime database collection
POST
/v1/servers/{serverId}/runtime/database/collectionsHow 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 |
|---|---|---|---|
| name | string | Yes | Human-readable name. |
| description | string | No | Human-readable description. |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
201Runtime database collection createdapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| serverId | string | No | Resource ID. |
| databaseId | string | No | Database ID. |
| collection | object | No | — |
| collection.id | string | No | Unique identifier. |
| collection.name | string | No | Human-readable name. |
| collection.description | string | No | Human-readable description. |
| collection.documentCount | integer | No | — |
| collection.createdAt | string | No | ISO 8601 timestamp. |
| collection.updatedAt | string | No | ISO 8601 timestamp. |
Create runtime database collection
Loading...
Response 201
Loading...