Skip to main content

Integration API: Phase 1.5 on staging (the full headless wizard)

Phase 1.5 of the headless Integration API is available on the staging sandbox. It lets an integration reproduce the entire operator wizard over the API, from discovering a category's fields to checking the same readiness numbers the wizard shows. These endpoints are on staging now and reach production at the Phase 1.5 release.

Superseded — now GA on production

Phase 1.5 went GA on production on 2026-07-03. See Integration API — Phase 1.5 GA on production. This post is kept for history.

Availability (historical)

The endpoints below were live on the staging sandbox (staging.traceable.digital) at the time of this post. They are now GA on production. See the Availability matrix.

New endpoints, mapped to the wizard steps

  • Discover (steps 1 to 3): GET /industries, GET /categories, GET /categories/{code}/schema let an ERP read exactly which fields a category requires and map its own columns against them. GET /suppliers returns the owned-or-linked suppliers, GDPR-minimised.
  • Author (step 4): PUT /products/{id}/form-data ingests fields in batches with fail-closed, per-field validation. Unknown fields are rejected, never silently dropped, and validation errors reference the field, never the value you sent.
  • Close the gates (step 5): POST /products/{id}/traceability, POST /products/{id}/components, and POST /companies/me/gs1-prefixes close the traceability, component, and GS1 ownership gates. GET /products/{id}/documents and GET /documents/{id}/download read evidence.
  • Check and submit (step 6): GET /products/{id}/readiness returns the completeness and compliance numbers the wizard displays, with the missing fields and gaps. Submit stays the same.
  • Withdraw: POST /products/{id}/withdraw pulls a published DPP under EU Battery Regulation Article 76; the public DPP then returns HTTP 410.

Scopes

The scope vocabulary grows to nine, adding dpp:withdraw, category:read, schema:read, and supplier:read alongside the existing five. Each is least-privilege: withdraw is separate from submit, supplier-read is separate from product-read. There is still no publish scope and no AI scope. See Scopes.

Read more