Create an organisation-scoped credential
An authorised workspace user creates an API key with explicit scopes. The secret is shown once and stored as a hash. Keep it on your server and revoke it when the integration no longer needs access.
Product Passport API
Connect product systems to the same controlled workflow
Use Passvanta's versioned REST API to connect product operations with your existing systems. Organisation scopes, review requirements and publication gates remain part of the integration.
Build an integration with a clear permission boundary
For engineering teams connecting PIM, ERP or internal product services through an API, and operations teams starting with structured CSV imports.
Connect product operations
Read and create products through the versioned API, keeping category and organisation context. The CSV import workflow reports results for individual rows so a malformed record does not hide the outcome of the rest of the file.
Carry evidence and review context
Use product, document and data-point operations to bring source information into the workspace. Export the passport and its provenance for downstream systems while respecting the same review and publication controls.
React to recorded lifecycle events
Subscribe an HTTPS endpoint to passport publication or registry registration events. Passvanta signs webhook deliveries; the receiving service can verify the signature before applying a change in another system.
Machine access remains attributable
API keys belong to one organisation and resolve to a service-account identity with explicit permissions.
Revocation disables subsequent authentication with that key; the raw secret cannot be recovered from storage.
Permission checks, validation and plan limits apply at the server boundary, including API calls.
Design the receiving system for real delivery conditions
The API is an integration surface; ready-made PIM or ERP connectors are not included. Clients should inspect operation-specific errors and retry rules. Webhook receivers should verify signatures and handle repeated events; do not rely on exactly-once delivery or a built-in durable redelivery queue.
FAQ
Questions about API integration
Can an API key access several organisations?
A key is created for one organisation. Integrations working with separate customer workspaces need an authorised credential for each relevant organisation.
Which webhook events are supported?
The current event types are passport.published and registry.registered. A registry event depends on an actual successful registration through a configured connection; subscribing to it does not activate that connection.
Can I start without building an integration service?
The integrations workspace includes a CSV product import with results per row. It provides a starting point for structured product entry while you plan API authentication and downstream handling.
Continue through the product workflow
Compliance Engine
Bring requirements, source documents and review decisions into one product workspace. Every missing value or unresolved evidence requirement has a place in the preparation workflow.
Compliance Engine →Digital Product Passports
A passport connects accepted product information to a stable public address. Passvanta keeps the published revision, the evidence behind it and the publication decision traceable.
Digital Product Passports →Supplier Portal
Turn missing product fields into a focused request. Suppliers see the requested information and submit their answers; your team keeps control of the review and product record.
Supplier Portal →Start an integration with its own scoped credential
Open integrations to manage keys, import a product file or register a signed webhook destination.