DataMatrix barcode API for vector PDF output
Render DataMatrix and GS1 DataMatrix barcodes in PDF labels and documents for product, medical, retail, and warehouse workflows.
/api/v1/pdf/render Render DataMatrix or GS1 DataMatrix payloads as vector PDF barcode elements inside product labels, warehouse labels, or documents while your system owns the encoded business payload.
When to use this API
- You need a 2D DataMatrix barcode in a PDF document or label.
- Your application already knows the encoded identifier, lot, serial, or product payload.
- You need repeated DataMatrix label layouts through Template Render.
- You want vector barcode output instead of raster images embedded in a PDF.
What it does not replace
- You need regulatory certification, device labeling approval, or GS1 certification from gPdf.
- You need gPdf to generate business identifiers or check external registries.
- You need scanner fleet management.
Which endpoint to call
/api/v1/pdf/render
JSON Render is the default path for this workflow.
/api/v1/template-render
Use this when the workflow needs the related API path, template contract, or capabilities lookup.
Minimal request
POST /api/v1/pdf/render - GS1 DataMatrix barcode on a product label.
{
"pages": [
{
"size": "label_100_100",
"elements": [
{
"type": "barcode",
"format": "gs1-datamatrix",
"content": "(01)09506000134352(10)LOT26A",
"x": 10,
"y": 14,
"width": 34,
"height": 34
},
{
"type": "text",
"x": 10,
"y": 56,
"content": "GTIN 09506000134352\nLOT LOT26A",
"style": { "font_size": 9, "font_family": "NotoSans-Regular" }
}
]
}
]
}
What gPdf handles
- Vector DataMatrix and GS1 DataMatrix barcode rendering in PDFs.
- Label or document layout around the barcode.
- Template binding for repeated product or warehouse labels.
- Binary PDF output for print, archive, or download workflows.
What your system owns
- Encoded payload content, application identifiers, serials, lots, and regulatory text.
- Scanner testing, module size validation, label stock, and acceptance criteria.
- Any industry-specific compliance workflow that consumes the barcode.
Production checklist
- Verify payload syntax before rendering.
- Print and scan at production size, DPI, and material.
- Test long identifiers and multiple product-language variants.
- Keep certification and regulatory review outside gPdf.
- Use Template Render for approved label families.
Claim boundaries
- gPdf renders DataMatrix barcodes; it does not certify regulatory compliance.
- Your system owns barcode payload semantics and scanner acceptance.
- Vector rendering does not replace physical print validation.
DataMatrix in PDF is a rendering job
DataMatrix barcodes often carry product or logistics identifiers. The important boundary is the payload. gPdf renders a vector barcode from the value you send; your system decides what the value means and whether it satisfies external requirements.
FAQ
- Does gPdf support DataMatrix barcodes?
- Yes. The public schema lists datamatrix and GS1 DataMatrix barcode format aliases.
- Does gPdf validate regulatory content?
- No. gPdf renders the barcode. Your system owns payload correctness and regulatory review.
- Can DataMatrix labels use Template Render?
- Yes. Use Template Render when a repeated label layout should accept only business data.
- Do I still need scan testing?
- Yes. Always validate with production printers, materials, and scanners.