OriginChainDB
Database endpoints

Set namespace capacity

Set or remove the record-capacity declaration for a vector namespace.

POST /v1/tenants/{tenant}/vector-indexes/{index}/namespaces/configure

Declare a namespace's record capacityRemoving this declaration does not make the database unlimited.
  1. Select the namespaceLocate it inside its vector index.
  2. Set or remove capacitySend a positive declaration, or null to remove it.
  3. Read the saved declarationA value below current usage is rejected.

Before you start

Use your database bearer token.

Connection setup

Use an existing namespace. A declared capacity cannot be smaller than its current usage.

Path parameters

FieldTypeRequired
tenantstringRequired
indexstringRequired

Headers

FieldTypeRequiredDescription
x-oc-db-userstringOptionalActing database user (role, grant and row-policy checks). Send with x-oc-db-key.
x-oc-db-keystringOptionalAPI key of the x-oc-db-user user.

Request body

application/json

Limits and accepted values
  • declared_capacity must be sent: an integer 1-9007199254740991 sets it, null removes it, absent answers 400.
  • A value below current usage answers 409.
  • dry_run: true is refused with 400.
  • Naming another namespace field answers 400 immutable_field.
FieldTypeRequired
declared_capacityintegerOptional
dry_runbooleanOptional
namestringRequired

Read the result

Check declared_capacity in the returned namespace. A number sets the declaration and null removes it. This value is not a statement that the database has unlimited capacity.

Response statuses

HTTP status reference
StatusWhat to do
200OK
400Correct the request before retrying.
401Check the credential and Authorization header.
402Check feature access or available credits.
403Check tenant access, roles and permissions.
404Check the resource ID and API route.
409Resolve the conflict before retrying.
413Split or reduce the request body.
415Send the required Content-Type.
422Correct the values or unsupported combination.
429Honor Retry-After when present; back off.
500Check the outcome before retrying a write.
501Check deployment support for this operation.
503Honor Retry-After when present; check write outcomes.
ยฉ 2026 Silicoyn Technologies Pvt Ltd