You can now send unit values through the Create Lab Test and Upload/Update Pre-Created Lab Test APIs, even when the test properties and conditions aren't configured on the platform.

You can now use the new issue_date field in Purchase Order (PO) V3 API to specify when a PO was issued in your system.

You can now send sampleName instead of sample numbers in the Upload/Update Pre-Created Lab Test and Create Lab Test APIs, so each test result is tied to a descriptive sample name that matches a specific lot or batch.

You can now link BOM components to your Material Library and Supplier Management records directly through the BOM Integration API, using materialCustomId and orgCustomId.

You can now store confirmation and approval dates directly on purchase orders through the Purchase Order (V3) API, in addition to entering them manually on the UI or via PO file import.

You can now create, read, and replace critical quality points (CQPs) for Style, Item, and Material directly from your own systems, so you no longer need to enter or upload them through the UI.

You can now retrieve reason codes for aborted, waived, rejected, split, and reset inspections through the List Inspections and Get Inspection API endpoints.

You can now create, update, delete, list, and get taxonomy categories for style/item and material taxonomies through the Taxonomy Category APIs, so you no longer need to rely on CSV uploads or UI edits to keep your product classifications current.

You can now update the product list, including item, style, or material details, directly through the same Upload/Update Pre-Created Lab Test API you already use to send test data.

Once your CPSC eFiling data mapping is configured, you can call the Get CPSC eFiling Data API endpoint to retrieve structured, compliance-ready certificate data for one or more completed lab tests, formatted for whichever filing method you use: CPSC Product Registry, Reference PGA Message Set, or Full PGA Message Set.