API errors

Forbidden

HTTP 403 ยท type https://qrbolt.com/developers/errors/forbidden

What it means

The operation is not allowed, for example a plan rule (such as a plan without batch barcode export), a department this key cannot use, or a GTIN whose code belongs to another department of your organization. reason, when present, says which rule.

What to do

Check detail and reason. For department rules, use a key for the right department or for the whole organization. For item-limit-exceeded, discontinue items you no longer use or upgrade the plan. For draft-release-needs-items-write, use a key with items:write, or release the item first. For read-only-plan or batch-export-not-enabled, change to a plan that includes Barcode Manager or batch export.

Reasons

Some of these problems carry reason (or code on a conflict) with one of these values. Branch on it as on type; the values never change.

item-limit-exceeded
The plan has no room for more Barcode Manager items. Only units count (packs and cases are free), and only while they are not discontinued. limit, current, requested and shortfall give the numbers. Nothing was created; in an import job the rows that did not fit are notProcessed.
draft-release-needs-items-write
Downloading or exporting the barcode of a DRAFT item releases it (it becomes LIVE and its GTIN locks), which is a change and needs the items:write scope. A key with only barcodes:read can download LIVE and DISCONTINUED items. A spec-sheet export releases nothing.
read-only-plan
The plan no longer includes Barcode Manager (after a downgrade), so items are read-only. Barcodes of LIVE and DISCONTINUED items still download; a DRAFT is refused, because downloading it would release it. The key's scopes do not change this.
batch-export-not-enabled
The plan does not include batch barcode export (ZIP, label sheets and spec sheets), so POST /v1/items/jobs/export is refused. Single barcode downloads still work.

All error types