Connect your ERP, PIM and shop to compliant EU DPPs.
Push product master data into EU Digital Product Passports today through our REST API, OpenAPI 3.1 spec and CSV / Excel / JSON import and export. Named ERP, PIM, PLM and commerce connectors are on the roadmap.
Three connectors on our roadmap for production DPP rollouts.
Planned data flows for teams launching their first wave of ESPR passports. Today you can wire any of these to our REST API and OpenAPI spec.
Sync product master data and supplier hierarchies.
- Planned: sync of materials and SKU variants with SAP S/4HANA
- Planned: ingest supplier hierarchies and production batches from MM and PP
- Today: drive the same flows through our REST API and OpenAPI spec
Pull released records, financial data, and compliance documents from Dynamics 365.
- Planned: released-product and variant mapping from Dynamics 365 Supply Chain
- Planned: connect to Dataverse and Power Platform
- Today: import via CSV / Excel / JSON or the REST API
Consolidate passport data and compliance analytics in your warehouse.
- Planned: replication into Snowflake
- Today: export to CSV / Excel / JSON-LD for your warehouse
- Today: read every published passport as machine-readable JSON-LD
The connectors we are building.
Grouped the way you think.
Eight categories of connectors on our roadmap. Need one of these today? Our REST API and OpenAPI spec, plus CSV / Excel / JSON import and export, already cover it.
Connect to your financial and operational backbone.
Pull product attributes and bill of materials at the source.
Replicate passport telemetry into your warehouse.
Share compliance evidence with customers and channels.
Collect supplier data through the networks you already use.
Align passports with your existing ESG reporting machinery.
Bring passport approvals into the tools your teams already use.
SSO, MFA, and provisioning driven by your IdP.
REST. OpenAPI. Agentic.
Built in from day one.
Every passport, export, and supplier feature sits behind the same REST API our own product uses, described by a public OpenAPI spec at /api/openapi.json. Authenticate with an API key (Bearer). Generate a typed client in any language from the spec, and point an LLM agent at our /llms.txt operator guide to run the entire workspace over REST.
Read the API docs →REST API
Resource endpoints, cursor pagination, and idempotency on every write. Authenticated with an API key (Bearer).
OpenAPI spec
A public OpenAPI spec at /api/openapi.json - generate a typed client in any language, no SDK lock-in.
Agentic by design
Point Claude Code, Codex or any LLM agent at /llms.txt and it can run the whole workspace over REST.
Import & export
CSV / Excel / JSON import; export to CSV / Excel / PDF / JSON-LD / QR. Every published passport is resolvable as JSON-LD.
The questions platform
teams ask us most.
What we don't cover natively, the API covers. What the API doesn't cover, we build alongside your team during onboarding.
Book a technical briefing →Do you support custom integrations on our internal systems?+
Yes. Everything in the product is exposed through the same public REST API, described by an OpenAPI spec at /api/openapi.json. Teams build custom integrations against internal systems (homegrown ERPs, bespoke PLMs, data buses) by generating a typed client from the spec. Enterprise plans include engineering support for the first two rollouts.
What authentication methods are supported?+
The API uses an API key (Bearer) today: each workspace issues a master key with workspace-level scope. SSO (SAML / OIDC) and SCIM provisioning are on our roadmap for Enterprise.
Is there a sandbox environment for testing?+
Every paid account gets an isolated sandbox tenant - identical to production for schema, integrations, and the public viewer, but fully separated from regulator indexes. Sandbox environments support webhooks, API keys, and full passport editing.
Can we embed the public passport widget on our own site?+
Yes. We ship an embeddable JavaScript widget and a native Web Component. Both inherit your brand tokens, are fully WCAG 2.1 AA compliant, and render offline-first for low-connectivity regions. Every passport also retains a persistently resolvable public page on your own custom domain.
What is the API rate limit and how is it scoped?+
The API enforces a per-key rate limit with rolling per-second windows rather than rigid buckets, so short bursts are tolerated. We return RFC-compliant RateLimit-* headers so your client can throttle adaptively.
Where is our data hosted?+
Customer data is processed and stored exclusively inside the EU - Frankfurt primary, Amsterdam failover. No copies, replicas, or backups leave the region, including for any integration traffic.
Related DPP resources
Go deeper on the regulation, the real cost and the technical build - or jump straight to the platform.
- DPP Readiness CheckScore your readiness in 10 questions and see the honest EU deadline for your product group.
- Packaging DPPPPWR packaging passports: recycled content, recyclability and the data carrier you need.
- Electronics DPPElectronics DPP: RoHS, WEEE, repairability and critical raw materials, mapped to ESPR.
- ERP/PIM IntegrationConnect ERP and PIM so passport data flows in automatically instead of being re-keyed.