Changes and notices

Every change to the API, newest first, with the date it takes effect. Additions don't change the version. A breaking change comes as a new version (/v3), announced six months ahead, and each version is supported for at least 12 months after its successor ships. Organizations' developer contacts are emailed about every notice.

November 12, 2026: v1 compatibility in the reference

  • New: the v1-compatible APIs (catalog v1, certificates v1, community and the TA API v1.5) in Reference and explorer, each endpoint with Try it: choose v1 compatibility at the top. Their description is at /v1/openapi.json.

November 12, 2026: community demand

  • New: Connect's community API (POST /api/v1/community/requests, GET /api/v1/community/activity) at this host, and GET /v2/demand for technical administrators.

November 12, 2026: the certificate and catalog APIs v1, complete

  • New: callback_email and /api/cov/generate-zip in the certificate (COV) API v1; retrieve answers for certificates Connect made too.
  • New: brand_logo_url in the catalog API v1.

November 12, 2026: more changes for technical administrators

  • New: POST /v2/facilities (match first, then create, with your own facility ID), countries of origin (GET and POST /v2/products/{id}/countries-of-origin), remove_categories on a product, a client's contacts by role (PUT and DELETE /v2/clients/{id}/contacts/{role}), and POST /v2/clients/{id}/hold-all and /withdraw-all.
  • TA API v1.5 at this host: /client and /brand writes, and /facility for a facility not registered yet.

November 11, 2026: client libraries

  • New: client libraries for TypeScript, Python and C#, generated from the API's description. See Client libraries.
  • Faster: /v2/catalog/brands with q answers in under a second.

November 11, 2026: the TA API v1.5 at this host

  • New: /services/oauth2/token and /services/apexrest/nongmoservices/*, answering as the Salesforce TA API v1.5 does, for TAs whose sign-in staff have set up. See Moving from v1.

November 11, 2026: Connect's catalog and certificate APIs on FIP-OS

  • New: the Verified Products catalog API v1 (/api/v1/catalog/*) and the certificate (COV) API v1 (/api/cov/* and the old /api/1.1/wf/* addresses), answered as Connect answers them. See Moving from v1.
  • Fixed: searching by name (q) in /v2/catalog/products and /v2/catalog/brands found nothing without a staff token.

November 11, 2026: changes for technical administrators

  • New: PUT and PATCH /v2/products/{id}, packages (POST /v2/products/{id}/packages, PATCH and DELETE /v2/packages/{id}), verifications (POST /v2/products/{id}/verifications, PATCH /v2/verifications/{ref}, and the actions hold, release, withdraw, terminate, transfer, cancel and renew), facilities on a verification (PUT and DELETE /v2/verifications/{ref}/facilities/{facility_id}), clients (POST /v2/clients, PATCH, withdraw) and brands (POST /v2/brands), with POST /v2/batch, Idempotency-Key and If-Match. In the sandbox now; in production each kind is switched on separately.

November 11, 2026: webhooks

  • New: webhooks for verification.status_changed, verification.expiring, certificate.issued, certificate.pdf_ready, opportunity.shared, opportunity.updated, client.application_reviewed and catalog.listing_changed: signed with HMAC-SHA256, retried for 24 hours, with a delivery log, replay and test. Manage them with /v2/webhooks (scope webhook.manage) or on Keys and tokens.

November 11, 2026: verification management and prospects (reads)

  • New: for technical administrators, /v2/clients, /brands, /products (with /products/{id}/packages), /verifications (with their facilities and history), /facilities, /certificates, and certificate PDFs with POST /v2/certificates/pdf. A TA's key sees only its own TA's records.
  • New: /v2/opportunities, the opportunities shared with your TA.
  • Coming next: writes, webhooks, the v1-compatible endpoints, and client libraries.

November 11, 2026: v2 opens, with the catalog

  • New: /v2/catalog/products, /products/{id}, /brands, /brands/{number}, /categories, /lookup, /changes and /export.
  • New: signing in with client credentials (a secret or private_key_jwt), explorer tokens on this site, and personal tokens.
  • New: the sandbox, at /sandbox/v2.
  • Coming next: verification management for technical administrators (reads, then writes), prospects, certificate PDFs, webhooks, the v1-compatible endpoints, and client libraries for TypeScript, Python and C#.

No notices are in effect.