API-only authenticity platform

Run product verification from your own systems.

PAQGEN can be sold and used as an API-first authenticity layer. Brands connect factory, ERP, label, packaging, ecommerce, or warehouse systems to create products, generate unit QR codes, print labels, verify scans, and monitor volume without using the operator console every day.

What the API can manage

The API covers the complete authenticity workflow. The operator console is available for teams, but an approved brand can run the same core operations from its own software.

Companies and users

Create approved workspaces, map users to a company, and keep each brand's data separated.

Product catalogue

Create or import product names, SKU codes, GTINs, pack sizes, origin, and customer-facing details.

Packaging designs

Upload label, pouch, sleeve, carton, or PDF packaging files and link them to product profiles.

QR placement

Save exact QR position, size, and margin so printed output stays consistent.

Production runs

Generate one unique secure token per physical product unit with batch/run references.

Printing

Render one serial on demand for factory printing, or create a small review PDF when suitable.

Customer verification

Verify genuine first scans, already-scanned codes, and invalid tokens from public QR scans.

Reports and volume

Read generated codes, first scans, repeats, invalid attempts, unused codes, and total activity.

Scale controls

Use plan-based limits for QR volume, users, API usage, storage, and production throughput.

How the token works

PAQGEN creates an approved company workspace and an integration user. That user logs in with email and password. The login response returns a token. Your system stores that token securely and sends it on protected API calls as Authorization: Bearer <token> with the company code in x-company.

1. Login and receive token

POST https://api.paqgen.com/api/admin/login
Content-Type: application/json

{
  "email": "integration@brand.com",
  "password": "approved-password"
}

Response:
{
  "token": "eyJhbGciOi...",
  "user": {
    "email": "integration@brand.com",
    "company": "brand_code",
    "role": "operator"
  }
}

2. Use token on protected calls

Authorization: Bearer eyJhbGciOi...
x-company: brand_code

API production flow

Create product

Send product name, brand, SKU, pack size, origin, and customer-facing details.

Upload packaging

Upload the packaging design and link it to the product profile.

Set QR placement

Save the QR x/y position and size for that packaging design.

Create production run

Create one unique QR record per physical product unit.

Print one unit

Request the printable output for serial 1, then serial 2, then serial 3.

Import sale data

Send POS or ERP sale rows so PAQGEN knows which units were sold.

Printing through API

For large production runs, do not generate one huge repeated packaging file. Your system asks PAQGEN for the current unit, prints it, then asks for the next serial. This works for office print-to-file and can also power a factory print-station app. Maximum QR volume is controlled by the approved plan and production setup, not by duplicating packaging pages.

Generate QR records

POST /api/batches
Authorization: Bearer <token>
x-company: brand_code

{
  "design_id": 42,
  "quantity": 50000,
  "product_code": "LINE-A",
  "batch_seq": 12
}

Print current unit

GET /api/batches/88/print-unit?serial=1
Authorization: Bearer <token>
x-company: brand_code

Response:
{
  "file": "/renders/brand/unit-1.pdf",
  "serial_no": 1
}

Sale and POS integration

Import sold-unit data from POS, ERP, ecommerce, or warehouse systems. This lets PAQGEN distinguish QR codes that are only packed from QR codes that were actually sold.

Import sold units

POST /api/batches/sales/import
Authorization: Bearer <token>
x-company: brand_code

{
  "items": [
    {
      "batch_id": "batch-uuid",
      "serial_no": 124,
      "barcode": "5012345678901",
      "sold_by": "Tesco Stevenage",
      "sale_reference": "POS-1001"
    }
  ]
}

Response:
{
  "imported": 1,
  "updated": 1
}

Core endpoints

POST/api/admin/login

POST/api/products

Create product profile details shown on scan pages.

POST/api/products/import

Import many product profiles from structured product data.

POST/api/designs/upload

Upload packaging design and link it to a product.

POST/api/designs/:id/placement

Save QR position and size on packaging.

POST/api/batches

Generate unique QR records for a production run.

GET/api/batches/:id/print-unit?serial=1

Render one printable unit output on demand.

POST/api/batches/sales/import

Import sold-unit data from POS, ERP, ecommerce, or warehouse systems.

POST/api/verify

Verify a customer scan and record genuine, repeat, or invalid.

GET/api/reports/metrics

Read generated, verified, repeat, invalid, unused, and total scan metrics.

API access

Request API-only access

Tell us the system you want to connect, expected QR volume, printing setup, reporting needs, and whether you need a browser workflow, print-to-file, or a factory print station.