Barcode Generator — 15 Symbologies, Check Digits Actually Validated

Barcode Generator renders EAN-13, UPC-A, Code 128, QR and 11 other barcode types as PNG images, with retail check digits validated, at $0.0015 per barcode on the Apify Free plan.

• Price: $0.0015 per barcode rendered on the Free plan, less on paid plans. Invalid data and wrong check digits are not charged.
• Example input: { "items": [{ "text": "4006381333931", "type": "ean13" }] }
• Output fields: text, ok, type, pngUrl, bytes, error

Generate barcode PNGs by API across 15 symbologies: QR, Code 128, EAN-13, EAN-8, UPC-A, UPC-E, Code 39, Code 93, ITF-14, Interleaved 2-of-5, MSI, Codabar, Data Matrix, PDF417, Aztec. Built on bwip-js (pinned 4.7.0), the reference barcode engine — which means retail codes get real check-digit validation: an EAN-13 with a wrong check digit is rejected with an error, not rendered into a barcode that scanners will reject at the till. Up to 50 per run, PNGs delivered as hosted URLs. Online, by API, or as an agent tool via Apify MCP.

Which symbologies validate vs just encode — stated plainly

• Validated (structure + check digit enforced by the engine): EAN-13, EAN-8, UPC-A, UPC-E, ITF-14 — wrong length or wrong check digit = rejected free. Our release test proves it: 4006381333931 renders, …930 (corrupted check digit) is refused.
• Encoded with internal checksums the engine computes for you: Code 128, Code 93, PDF417, QR, Data Matrix, Aztec (their checksums/ECC are part of the format — you can't get them wrong).
• Rendered as given (no check digit in the standard, or optional): Code 39, Codabar, MSI, Interleaved 2-of-5 (non-ITF14). These encode what you send.

What you get

• pngUrl — a hosted PNG per barcode (signed URL from the run's key-value store) + bytes
• Options: scale (1-10), height (linear codes), includeText (human-readable line)
• Mixed batches: per-item type overrides the run default
• Fail-soft: invalid data for a symbology never fails the run — {ok: false, error} with the engine's exact reason, never charged.

Input

{ "items": [
  { "text": "4006381333931", "type": "ean13" },
  { "text": "https://yoursite.com/p/123", "type": "qr" },
  { "text": "PKG-2024-00042", "type": "code128" }
] }

Output (real run)

{
  "text": "4006381333931",
  "ok": true,
  "type": "ean13",
  "pngUrl": "https://api.apify.com/v2/key-value-stores/.../records/barcode-1-ean13-4006381333931.png?signature=...",
  "bytes": 2748
}

Pricing

$0.0015 per barcode rendered on the Apify Free plan, billed as the barcode-generated event. Paid Apify plans pay less ($0.0014 Bronze, $0.00131 Silver, $0.0012 Gold, $0.0011 Platinum, $0.001 Diamond). No start fee. Invalid data and wrong check digits are never charged. A full 50-barcode run costs $0.075 on the Free plan.

Honest limits

• PNG output only (no SVG/EPS yet).
• PNG URLs are signed store links tied to your run's storage retention — download them into your own storage for long-term use.
• GS1 application-identifier composition (GS1-128 with AIs) is not assembled for you — send the full encoded string.

FAQ

What happens if I send 12 digits for EAN-13? bwip-js computes the check digit for you and renders a valid 13-digit code. Send 13 and the last digit is verified — mismatch = rejection, not a broken label.

Can I mix symbologies in one batch? Yes — per-item type; the run-level type is just the default.

Are the QR codes scannable at print size? Use scale 3+ for print (each module ≥3px); the default is print-safe. Error correction is the engine's standard level.

Which type should I use for internal SKUs? Code 128 — full ASCII, compact, and its checksum is computed automatically.

Why did some rows come back ok: false? The data was invalid for that symbology (wrong length, wrong charset, wrong check digit) — the error is the engine's exact reason. Never charged.

Use from code or AI agents

curl -s "https://api.apify.com/v2/acts/EliAI~barcode-generator/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -X POST -H 'Content-Type: application/json' \
  -d '{"items": [{"text": "4006381333931", "type": "ean13"}]}'

Agents: connect Apify MCP and call the EliAI/barcode-generator tool.

• Capability: render barcode PNGs across 15 symbologies with engine-level validation (check digits enforced on retail codes)
• Required input: text (string) or items (array); optional type (default code128), scale, height, includeText
• Returns: one record per barcode; pngUrl is the deliverable
• Bounded: 50 barcodes per run; failures isolate per item
• Side effects: PNGs written to your run's own key-value store only

Who uses it

• E-commerce sellers generating EAN-13 and UPC-A barcodes with check digits validated before printing labels
• Warehouse teams producing Code 128 and ITF-14 barcodes for cartons and shelves
• Developers adding barcode PNGs to invoices or packing slips through an API call
• Event organizers creating PDF417 or Aztec codes for tickets
• Inventory app builders batch-generating Data Matrix codes for asset tags