A Digital Product Passport API lets your systems create and update passport data, upload evidence, trigger validation and publish approved versions without manual entry. DPP Shield exposes scoped API keys, signed webhooks, imports and EPCIS event exchange for that integration.
What can you automate through the API?
Typical flows create or update products and passports, attach supplier documents, read validation findings, and publish an approved public version. Signed webhooks notify your systems when a passport is published or revalidated, so downstream catalogues stay in step.
How is access controlled?
Access uses per-workspace scoped API keys, with rate limits and available operations set by the plan. Publishing keeps the platform's review and step-up rules, so automation cannot bypass the controls that protect a public claim.
How does it fit existing systems?
Connect a PIM or ERP as the source of product data, keep DPP Shield as the passport system of record, and use imports and EPCIS exchange for bulk and event-based data. Identifiers and the public URL stay stable across updates.
Frequently asked questions
Is the API available on every plan?
API access, rate limits and bulk operations depend on the configured plan and integrations.
Can automation publish without review?
No. Publishing still applies the platform's validation and second-factor rules; the API automates the work around those gates, not the gates themselves.