OriginChainDB
Database endpoints

Check a background job

Check the state and progress of a filtered vector-record update or delete job.

GET /v1/tenants/{tenant}/vector-indexes/{index}/jobs/{job_id}

Separate job progress from completed changesA stopped or limited job may have already changed records.
  1. Use the returned job IDIdentify the filtered update or delete.
  2. Inspect state and progressCompare examined, matched and applied work.
  3. Decide whether to continueBase follow-up actions on the reported outcome.

Before you start

Use your database bearer token.

Connection setup

Use the job ID returned by a filtered vector-record update or delete on this index.

Path parameters

FieldTypeRequired
tenantstringRequired
indexstringRequired
job_idstringRequired

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.

Read the result

Check state together with progress. Examined or matched records are not the same as updated records. A stopped or limited job can have applied some changes already.

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.
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