curl -X POST "https://api.scanova.io/media/bulk/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{ "count": 25 }'
{
"id": 12,
"operation_id": "BM-9F3K2LQP",
"status": "new",
"count": 25,
"upload_count": 0,
"created": "2026-09-08T09:00:00Z",
"modified": "2026-09-08T09:00:00Z"
}
Media Library
Create a bulk media batch
POST /media/bulk/
POST
/
media
/
bulk
/
curl -X POST "https://api.scanova.io/media/bulk/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{ "count": 25 }'
{
"id": 12,
"operation_id": "BM-9F3K2LQP",
"status": "new",
"count": 25,
"upload_count": 0,
"created": "2026-09-08T09:00:00Z",
"modified": "2026-09-08T09:00:00Z"
}
Reserves a batch for a set of related file uploads, on the Management API host (
api.scanova.io), authenticated with your raw Management API key.
POST https://api.scanova.io/media/bulk/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
integer
The number of files you plan to upload into this batch — used to pre-check the account’s
BULK_MEDIA quota before you start uploading.curl -X POST "https://api.scanova.io/media/bulk/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{ "count": 25 }'
{
"id": 12,
"operation_id": "BM-9F3K2LQP",
"status": "new",
"count": 25,
"upload_count": 0,
"created": "2026-09-08T09:00:00Z",
"modified": "2026-09-08T09:00:00Z"
}
operation_id is generated server-side. After creating a batch, upload each file via Upload a file with bulk_media set to this batch’s id.
403 if the account has already exhausted its BULK_MEDIA upload quota for the given count:
403
{ "detail": "You have exhausted your limit of 100 Bulk Media uploads.", "limit": 100 }
Related
- List bulk media batches — see existing batches.
- Upload a file — upload into this batch.
- Management API overview — the auth scheme and quota rules that apply to this endpoint.
Authorizations
Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: 401f7ac837da42b97f613d789819ff93537bee6a. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. api.scanova.io) — the same key sent to the regular API host will not authenticate.
Response
Batch created.
Was this page helpful?