OriginChainDB
Database endpoints

Store vectors in bulk

Stores up to 100,000 dense vectors in a vector collection as one atomic batch.

POST /v1/tenants/{tenant}/vector/{table}/put_bulk

Load vectors as one atomic batchSend a vectors envelope with shared configuration, not a bare array.
  1. Match the shared configurationUse compatible dimension, metric and index settings.
  2. Supply the vector batchInclude each vector's ID, embedding and optional metadata.
  3. Check the inserted totalRead accepted count and processing time.

Before you start

Use your database bearer token.

Connection setup

Use a collection whose dimension matches the vectors. Send the vectors envelope shown in the example, not a bare array.

Path parameters

FieldTypeRequired
tenantstringRequired
tablestringRequired

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
  • Envelope object, not a bare array.
  • More than 100,000 vectors is a 413;
  • an empty `vectors` list answers inserted 0.
  • metric / quantization / index take the same values as the single put.
  • `expected_generation` makes the write conditional on the collection's index generation (409 on mismatch).
FieldTypeRequired
dimintegerRequired
embedderstringOptional
expected_generationstringOptional
indexstringOptional
metricstringOptional
quantizationstringOptional
vectorsobject[]Required
Fields in vectors
FieldTypeRequired
embeddingnumber[]Required
Fields in embedding
FieldTypeRequired
embeddingnumberOptional
FieldTypeRequired
idstringRequired
metadataobjectOptional

Read the result

inserted reports the accepted vectors and elapsed_ms reports processing time. The body needs a vectors envelope with shared configuration; it is not a bare array of embeddings.

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.
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.
503Honor Retry-After when present; check write outcomes.
© 2026 Silicoyn Technologies Pvt Ltd