We're deprecating the auth/login endpoint in favor of using apikey authentication for the following reasons:

• Enhanced Security: API keys, being long and random, offer better protection against unauthorized access compared to traditional passwords. They can also be easily revoked or rotated if necessary.

• Streamlined Simplicity: API keys simplify the authentication process, eliminating the need for complex login workflows, making integration more straightforward.

This transition will improve the security and efficiency of our API integrations.

We’re introducing the new fields system_updated_from and system_updated_to in the Report APIs and Inspection Management page to address the limitations shown by the existing updated_from and updated_to fields. The new fields will accurately track data events for each inspection and cover more use cases. This enhancement ensures that clients can efficiently access updated inspection data via API without disrupting the UI's inspection list.

For more details, refer to the Report APIs specification.

Link parent and child POs to efficiently manage relationships between master and split POs.

As master POs may sometimes be split into smaller POs for distribution to different locations, the Purchase Order Association APIs enable organizations to link the master PO and split POs to leverage the POs’ association in the T&A, as well as manage PO associations by retrieving and deleting PO association data.

For more details, refer to the Purchase Order Association APIs specification.

Introducing LabSync API, a solution for streamlined collaboration in the testing process. LabSync API enables uploading of test reports and test data, eliminating manual work for suppliers, factories, and labs. The Create/Update a Lab Test API allows labs to send test data to LabSync from their internal systems, centralizing information for easy stakeholder review. Moreover, the same API supports updates to submitted test reports, providing flexibility for adjustments while ensuring data accuracy.

For more details, refer to the Lab Test API specification.

Generate POs and retrieve PO data for integration with your internal systems using the new styleName field. Initially, the styleName data point could only be generated through manual input or file import. Inspectorio system now supports this field in the existing Purchase Order API integration to facilitate the display of meaningful names corresponding to style IDs.

For more details, refer to the Purchase Orders APIs specification.

To provide additional information about POs, Inspectorio system now supports the eventName attribute on the PO level, which stores the reference data of items included in the PO, such as the year, cycle, department code, and department name. A new column called PO_EventName was also added to our Purchase Order file template as an optional field. It will show as the "Event Name" column on the PO Management page. This new attribute can be leveraged to store other optional information.

For more details, refer to the Purchase Orders APIs specification.

Inspectorio system now supports the shipmentTerm field on the item level, which stores the reference data about the shipment term for each item included in the PO. Vendors can refer to the shipment term to create POs with correct items and quantities. The shipmentTerm attribute is an optional field, which can be leveraged to store other optional information.

For more details, refer to the Purchase Orders APIs specification.

As the standard version is being used for analytics purposes by some key clients, we have added version inside standard in the List Report API endpoint.

• API Method: List Report
• Attributes: version
• Description: When report data is pulled, standard version attribute will always be available in Rise API.

With an aim to support clients to get important information from form data, we have added total_available_capacity_in_units and total_number_of_employees inside formData in the GET Step Execution API endpoint.

• API Method: Get Step Execution
• Attributes: total_available_capacity_in_units, total_number_of_employees
• Description: If the assessments use Factory Capacity Form or Factory Information Form, these attributes will be available in Rise API.

With an aim to support clients to get important information related to metadata, we have added 8 new attributes inside capa and assessmentExecution in the GET Report API endpoint.

• API Method: Get Report
• Attributes: dueDate, escalatedBy, followUpType, assessmentLocation, assessmentDueDate, assignedUsers, declineReasons, version
• Description: When report data is pulled, these attributes will be available in Rise API.

For more details, please refer to the List Report API Guide found on this page.

To stay updated on the current production status of your T&As and effectively plan shipment activities, you have the option to obtain the production status of T&As on the item or PO level via API. By retrieving the latest production status via API, you can use the similar JSON structure to continue updating the production status or to sync up with your internal system. This seamless API integration facilitates a comprehensive workflow, minimizing the need for manual tasks and guaranteeing consistent and reliable data.

For more details, refer to the Time and Actions API specification.

Though it's possible to create purchase orders directly from Inspectorio system, most of the cases customers have purchase orders created from their systems then synced to Inspectorio's. The creation date refers to a date when purchase orders are written at customers'systems; and some customers use that date to calculate actual order lead time for their analysis. For this purpose, we introduced a new field clientCreatedDate in PO APIs as well as added a new column PO_ClientCreatedDate to our Purchase Order file template as an optional field.

For more details about the new field, please refer to the Purchase Order APIs specification.

For more information about the new column, please refer to the Specification in the PDF link.