Create a collection
POST/api/v1/collections
Creates a collection. name is unique per project; a second collection of the same name is 409 NAME_CONFLICT. A schema is compiled here, so one JSON Schema cannot parse is refused rather than stored.
Request
Responses
- 201
- 400
- 401
- 403
- 409
- 413
- 429
- 500
- 502
- 4XX
Collection created
Invalid request — a query parameter or body field the operation does not declare, or a value that fails validation
Authentication required
Insufficient permissions
A collection of this name exists in the project (NAME_CONFLICT)
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there