Overview
v2.0.0
Draft Specification
The BOMcheck Platform API (v2) is currently in active development and as is subject to change. Please see the Scope Roadmap for delivery timeline.
Accessing the API
Access to the Platform API is granted as a costed add-on to your existing BOMcheck account. Costs are tiered based on number of API requests to ensure fair access to all account sizes. Please contact our support team for more info.
Summary
The BOMcheck Platform API (v2) is being developed to allow the upload, processing and download of IPC 1752 standard XML files. Phase 1 (Submit/Request) of the Platform API was launched in Q4 2023. Further delivery of Platform API functionality will follow the Scope Roadmap.
There are four main BOMcheck features which users may interact with using the Platform API:
- Submit Declarations: Create RCDs and FMDs in the platform against the supported Declarable Substance Lists as per the BOMcheck Declaration Tools.
- Submit Supplier Requests: Launch Send Requests to Suppliers campaigns to collect compliance data from suppliers as per the BOMcheck Supply Chain Tools.
- Download Declarations: Download and consume supplier compliance declarations (RCDs and FMDs) as per the BOMcheck Retrieve Data Tools.
- Download Integration Data: Download a range of useful integration data including supported BOMcheck Substance and Exemption Lists, Lists of Suppliers and DUNs numbers etc.
Scope Roadmap
| Delivery Phase | Submit/Request | Submit/Declare | Download | Integrate |
|---|---|---|---|---|
| Phase 1 (2023/Q4) | 1752A/B Class C/D | - | - | Primary Substance & Exemption Lists |
| Phase 2 (2024/Q3) | - | 1752A/B Class C | - | CAS Numbers & Supplier DUNs |
| Phase 3 (2024/Q4) | - | 1752A/B Class D | 1752A/B Class C/D | Additional Substance Lists |
| Phase 4 (2025) | JSON standard | JSON standard | JSON standard | - |
The scope roadmap is subject to change without notice.
Feedback
You may influence the direction, scope and delivery of this API by creating an Enhancement Request in the SCN (more info here) and/or join the API Working Group by emailing JPearson@sphera.com with your contact information.