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

# Update a GS1 batch recall

> GET, PATCH /qr/gs1-recalls/{pk}/

Reads and updates one GS1 batch recall notice.

```
GET    https://api.scanova.io/qr/gs1-recalls/{pk}/
PATCH  https://api.scanova.io/qr/gs1-recalls/{pk}/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField path="pk" type="integer" required>
  The recall record's id.
</ParamField>

<ParamField body="is_active" type="boolean">
  Set to `false` to end the recall.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X PATCH "https://api.scanova.io/qr/gs1-recalls/12/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{
        "is_active": false
    }'
  ```
</RequestExample>

<Note>
  Deactivating is the intended way to resolve a recall — the row stays in place so the recall history is preserved and auditable. `gtin`, `batch_lot_value`, and `message` remain editable for corrections.
</Note>

## Related

* [List and create GS1 batch recalls](/api-reference/management-api/qr/gs1-recall-list-create) — the collection this record belongs to.
* [QR Manager overview](/api-reference/management-api/qr/overview) — the quotas, role permissions, and Trash model shared by every endpoint in this module.
* [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 GET /qr/gs1-recalls/{pk}/
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:
  /qr/gs1-recalls/{pk}/:
    get:
      summary: Retrieve a GS1 batch recall
      description: Reads one recall notice.
      operationId: getGs1BatchRecall
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
          description: The recall record's id.
      responses:
        '200':
          description: One recall notice.
          content:
            application/json:
              example:
                gtin: '01234567890128'
                batch_lot_value: LOT-2026-04
                message: >-
                  This batch has been recalled due to a labeling error. Contact
                  support.
                id: 12
                is_active: true
                created: '2026-09-09T09:00:00Z'
                modified: '2026-09-09T09:00:00Z'
        '404':
          description: No recall with this id for 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.

````