Product operations
Create and read product records while retaining their category and organisation context.
Developers
Connect product data without creating another silo
Use stable API resources to move products, evidence and passport operations into your existing systems.
A practical integration surface
Passvanta exposes versioned REST endpoints under /api/v1. API keys use the Bearer authentication scheme and remain scoped to an organisation.
Start with a product request
curl https://passvanta.com/api/v1/products \
-H "Authorization: Bearer pv_..."Evidence workflows
Connect documents, supplier responses and reviewed data points to the right product.
Events and webhooks
Subscribe systems to relevant lifecycle changes with signed delivery.
Portable exports
Export versioned passport data and its provenance for downstream use.
Built for controlled automation
Machine-readable errors support predictable handling.
Operations that require safe retries use explicit idempotency controls.
Rate limits and plan limits stay explicit.
Sensitive credentials never belong in browser code.
API access follows the same controls
An integration does not bypass review, tenant boundaries or publication gates. Actions remain attributable to the organisation and credential that initiated them.
FAQ
Integration questions
How are API keys scoped?
Keys belong to one organisation, carry explicit scopes and can be revoked. The secret value belongs in server-side secret storage, never in frontend code.
How should clients handle retries?
Clients should use the documented idempotency controls for write operations, respect rate-limit responses and retry transient failures with backoff.
What do webhooks contain?
Webhook subscriptions are limited to selected events. Deliveries are signed so receiving systems can verify origin before processing payloads.
Prepare your first integration
Create a workspace, generate an API key and test the product endpoint.