Order Feasibility API
Changelog
Current version 1.0
Learn more about how our versioning works
We’re constantly working to improve our APIs. Check this page regularly to find out what's new.
Here’s a summary of what's changed.
Version: 1.0
Release type: Stable
| Version | Specification update | Release date | Description | Impact |
|---|---|---|---|---|
| Order Feasibility v1.0.32 | 19 November 2024 | 19 November 2024 | Update: Details of error FCC-503-0 Service Unavailable have been added to the specification and Errors documentation. | A detailed description of error FCC-503-0 is now available in both the specification and the list of errors provided in the API documentation. |
| Order Feasibility API v1.0 Beta | n/a | 25 February 2024 | Fix: Mulesoft applied a fix for a known issue with syncing of client credentials causing problems with connectivity to the APIs. We will monitor to ensure there are no ongoing issues. | You will be able to reset your Client ID and Secret and connect to the API with the new credentials. |
| Order Feasibility API v1.0 Beta | 13 December 2023 | 25 February 2024 | Update: The following attribute names have been changed: - cseProductOfferDetails.cseProductOfferId is now called:cseProductOfferDetails.productOfferId- cseProductOfferDetails.cseProductOfferName is now called:cseProductOfferDetails.productOfferName | Attribute names are now aligned to the product catalogue model. Use the new attribute names for cseProductOfferDetails.productOfferId and cseProductOfferDetails.productOfferName |
| Order Feasibility API v1.0 Beta | 20 November 2023 | 20 November 2023 | New: This release includes: POST /orderFeasibility | Use the Order Feasibility API to: - request order feasibility status to check if an order is possible for an address or location - allocate resources to fulfil the request if the order is feasible and submitted. |
Last updated 19 November, 2024