Place 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 |
|---|---|---|---|---|
| Place 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'll be able to reset your Client ID and Secret and connect to the API with the new credentials. |
| Place API v1.0 Beta | 20 February 2024 | 25 February 2024 | Documentation updates: - Location descriptors was removed from test data, FP1. - Intact ONT: Type 120 and Active ONT: Type 120 were removed from test cases. | View updated test cases |
| Place API v1.0 Beta | 12 December 2023 | 25 February 2024 | Improvement: The productOrders.customerOrderRef attribute name has been changed to: productOrders.providerReference | Use the new attribute name for productOrders.providerReference |
| Place API v1.0 Beta | 12 December 2023 | 25 February 2024 | Improvement: Removed all label values in responses. This was changed because the response contains all information regarding the location. | Label values will no longer be included in responses. |
| Place API v1.0 Beta | 20 November 2023 | 20 November 2023 | New: This release includes:GET /placesGET /places/{id}GET /places/{id}/siteInformation | Use the Place API to get: - a list of places that match your search criteria - address details associated with a Place ID - Chorus network location information, details of ONTs, products, and open orders for a Place ID. |
Last updated 10 July, 2024