curl -X PATCH "https://api.scanova.io/bulk-operation/bo-8f3a1c/rename/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{ "name": "September event QR batch (final)" }'
{
"operation_id": "bo-8f3a1c",
"name": "September event QR batch (final)"
}
Bulk Operations
Rename a bulk operation
PATCH /bulk-operation//rename/
PATCH
/
bulk-operation
/
{operation_id}
/
rename
/
curl -X PATCH "https://api.scanova.io/bulk-operation/bo-8f3a1c/rename/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{ "name": "September event QR batch (final)" }'
{
"operation_id": "bo-8f3a1c",
"name": "September event QR batch (final)"
}
Renames a bulk operation, on the Management API host (
Unlike the generate/update/download/quick-action endpoints, renaming deliberately requires no
api.scanova.io), authenticated with your raw Management API key.
PATCH https://api.scanova.io/bulk-operation/{operation_id}/rename/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
string
required
The operation’s
operation_id, from List bulk operations.string
required
The new name.
curl -X PATCH "https://api.scanova.io/bulk-operation/bo-8f3a1c/rename/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{ "name": "September event QR batch (final)" }'
{
"operation_id": "bo-8f3a1c",
"name": "September event QR batch (final)"
}
BULK_OPERATION quota or plan permission beyond authentication — so an operation can still be renamed even after the account’s bulk operation quota is exhausted. 404 if operation_id isn’t an operation owned by this account.
Related
- List bulk operations — find the
operation_id. - 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.
Path Parameters
Response
Renamed.
Was this page helpful?