Version and errors
Use `/api/v1` with JSON content negotiation. Error responses include a stable code, message, request ID and field details where relevant.
- 4xx validation and authorization
- 409 conflict and idempotency
- 429 rate limit handling
API reference
Integrate product records with a clear contract
The public reference documents the supported contract; private tenant data and internal admin routes are never exposed as documentation.
Open API referenceReview before activation
Test with fictional products and a dedicated endpoint secret. Any production connection requires the customer plan, credentials and deliberate owner activation.
- No live claims in examples
- Signed webhook delivery
- Safe URL policy
Support the lifecycle
Product, evidence, passport, ownership, repair and webhook resources share the same public IDs and audit semantics.
- OpenAPI link
- Terms and acceptable use
- Contact for account access
Ready for a concrete next step?
Try the data-readiness assessment, inspect the live demo or talk to the team about your catalogue.
Open API reference Check readiness