The plant-passport layer for systems that don't have one.
Your system runs orders, stock and invoicing. FloraPass issues the passports — via API, under your customer's own operator registration, with public verification built in.
No sandbox to request. The reference is open — read it before you talk to us.
Plant-passport compliance never stops moving.
Building it once is the easy part. Staying correct is the part that stays on your roadmap for as long as you have EU customers.
The regulation changes
Reg. (EU) 2016/2031 has been amended, most recently by Reg. (EU) 2024/3115. Someone has to read each amendment and decide whether your output is still compliant.
The format is prescribed
Impl. Reg. (EU) 2017/2313 fixes the layout: the EU emblem, the wording, and elements A to D in a bordered block. It is not a design decision you get to make.
Protected-zone lists change
Protected-zone passports name the quarantine pests they cover, and that list is maintained by the Commission — not by you.
How it works with your product.
Keep the workflow your customers already know. FloraPass handles the passport lifecycle alongside it.
Connect the workflow you already use
Create, issue, replace and retrieve plant passports from your own product, without asking customers to re-enter the same order or stock information.
Keep each customer separate
Each professional operator works in its own protected account. One customer's passports and business records are never mixed with another's.
Use the printers they already have
Produce labels for everyday office and thermal printers, whether the customer needs one passport or a complete print run.
Make every label easy to scan
Add QR and barcode options that fit existing receiving and retail workflows, without designing a separate label system.
Give recipients a clear verification path
Buyers, inspectors and other recipients can verify a passport online without creating an account.
Handle busy periods without one-by-one work
Prepare and issue many passports together, so seasonal volume does not turn into repetitive manual work.
Read it yourself.
The full OpenAPI reference is public and needs no account, no NDA and no sales call. Every endpoint below is the one the product actually runs on.
Interactive API reference
Browse every endpoint, request shape and error code — and the raw OpenAPI document.
POST /api/passportscreate a draftPOST /api/passports/{id}/issueissue itGET /api/passports/{id}/labelPDF · ZPL · A4 2-up · GS1 QRPOST /api/passports/importbulk CSV, all-or-nothingGET /api/verify/{id}public, anonymous