New Features - Core API

7min

We’re excited to announce our latest Core API release! This release introduces new features in Order Service, Participant Service, and Dispatch Service. Read the section below for details.

Orders Service

Order On-hold State

This release introduced a new On-hold state for the State Machine API of Order Service. App developers can use this new state and develop apps that can handle situations where orders are temporarily withdrawn or put on hold.

Facility ID Support

App Developers can now pass the FacilityId within the Create Order API request in the location parameter for dropDetails, pickupDetails, and returnDetails. When developers pass a valid Facility ID, OS1 Platform will internally pick the associated Location ID and process the order.



Dispatch Service

Add Custom Business Logic

Previously, developers managing Dispatches to support custom business rules required building wrappers on OS1 Platform services for validation, which was not a developer-friendly experience. Developers can now use custom business logic rather than customized wrappers for handling dispatch services associated with their business. This is far more convenient for building a complete logistics solution including dispatch services.

We also developed and integrated a custom code library for different APIs associated with Dispatch Services that include Dispatch, Job, and Ledger. This change enables developers to inject custom business logic within the API lifecycle for custom validations and enrichment. This functionality supports use cases such as deciding whether a job can be assigned to a particular delivery agent based on tenant-owned business logic.



Participant Service

Update Core Attributes

Previously, if a developer created a vehicle with an incorrect owner, another vehicle object was required to fix it. Now, a developer can modify the different values of the owner in the original object.

With the transition to v2 of our Participant Service APIs, developers can now update Core Attributes' values such as Participant, Name, Participant Owner ID, Category, Sub-Category, and Template. This update works well for use cases that require changing these attribute values anytime during the participant object's lifecycle.



New Postman Collection

Click the Run in Postman button below to open a modal where you can fork our latest collection to your workspace and stay up to date with the latest changes.