> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Rename a bulk operation

> PATCH /bulk-operation/{operation_id}/rename/

Renames a bulk operation, on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key.

```
PATCH https://api.scanova.io/bulk-operation/{operation_id}/rename/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField path="operation_id" type="string" required>
  The operation's `operation_id`, from [List bulk operations](/api-reference/management-api/bulk-operation/list).
</ParamField>

<ParamField body="name" type="string" required>
  The new name.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  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)" }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "operation_id": "bo-8f3a1c",
    "name": "September event QR batch (final)"
  }
  ```
</ResponseExample>

Unlike the generate/update/download/quick-action endpoints, renaming deliberately requires no `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](/api-reference/management-api/bulk-operation/list) — find the `operation_id`.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota rules that apply to this endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json PATCH /bulk-operation/{operation_id}/rename/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    api.scanova.io (QR codes, folders, tags, leads, forms, analytics, plans,
    shared users & roles), plus the token-creation and usage-stats endpoints
    used to authenticate against it. Every path and request/response shape below
    was verified live against a real API key and the actual running backend
    (Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
  version: 2.0.0
servers:
  - url: https://api.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /bulk-operation/{operation_id}/rename/:
    patch:
      summary: Rename a bulk operation
      description: >-
        Renames a bulk operation record. Deliberately requires no BULK_OPERATION
        quota/permission beyond authentication, so a job can still be renamed
        after the account's quota is exhausted.
      operationId: renameBulkOperation
      parameters:
        - name: operation_id
          in: path
          required: true
          schema:
            type: string
      requestBody:
        content:
          application/json:
            example:
              name: September event QR batch (final)
      responses:
        '200':
          description: Renamed.
          content:
            application/json:
              example:
                operation_id: bo-8f3a1c
                name: September event QR batch (final)
        '404':
          description: No operation with this operation_id owned by this account.
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        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.

````