GTIN / EAN Barcode Validator

Validate GTIN-8, GTIN-12 (UPC-A), GTIN-13 (EAN-13) and GTIN-14 barcodes using the official GS1 mod-10 check digit algorithm — plus a GS1 prefix → Member Organisation lookup. Runs in Standby mode as a fast HTTP API. No login, no personal data.

Endpoint

GET /validate?gtin=<barcode>

Spaces and hyphens in the input are ignored.

Example

GET /validate?gtin=4006381333931

{
  "inputRaw": "4006381333931",
  "normalized": "4006381333931",
  "valid": true,
  "format": "GTIN-13 (EAN-13)",
  "length": 13,
  "checkDigitGiven": 1,
  "checkDigitExpected": 1,
  "gs1Prefix": "400",
  "gs1PrefixOrganization": "GS1 Germany",
  "prefixNote": "GS1 prefix identifies the GS1 Member Organisation that licensed the company prefix, not the country of manufacture.",
  "errors": []
}

An invalid code returns "valid": false with a reason in errors, for example a check-digit mismatch, a wrong length, or non-digit characters.

What it checks

• Length — must be 8, 12, 13 or 14 digits.
• GS1 mod-10 check digit — the standard right-anchored (weights 3,1,3,1…) checksum used by all GTIN formats. Detects every single-digit error and most transposition errors.
• GS1 prefix — for GTIN-12/13/14, the leading digits are mapped to the GS1 Member Organisation that issued the company prefix.

Note on the prefix: the GS1 prefix indicates the GS1 Member Organisation that licensed the company prefix — not the country where the product was manufactured. GTIN-8 uses a separate allocation scheme, so no prefix organisation is returned for it.

Response fields

Field	Description
inputRaw	Raw input as received
normalized	Input after stripping spaces and hyphens
valid	true if length and check digit are both valid
format	Detected GTIN format
length	Digit length after normalization
checkDigitGiven	Check digit present in the input
checkDigitExpected	Correct GS1 mod-10 check digit
gs1Prefix	First 3 digits of the GTIN-13 view (GTIN-12/13/14)
gs1PrefixOrganization	GS1 Member Organisation for that prefix
prefixNote	Clarification on what the prefix means
errors	Reasons the code was rejected, if any

Use cases

• Validate product barcodes before importing them into a catalog or ERP.
• Clean and de-duplicate marketplace / supplier feeds.
• Verify UPC-A (US) and EAN-13 (EU/rest of world) codes in one call.
• Check GTIN-14 case/carton codes in logistics data.

Pricing

Pay-per-event: $0.001 per API call (api-call).

Notes

This Actor performs offline algorithmic validation. A valid result means the barcode is structurally correct (well-formed and check-digit-consistent); it does not confirm that the code is registered to a real, active product in the GS1 GEPIR registry.