Changelog

v1.0.1 / 2021-01-21

Non-breaking changes:

Fixed an issue where specific queries for individual place records returned an error due to a null gridReference property.
Fixed an issue where queries for individual place records that did not exist returned a 500 HTTP status code instead of the appropiate 404 status code.

This update marks the official public release of the Logainm API.

Breaking changes:

Pagination is now enforced for all requests to API endpoints returning a list of results. If no page parameters are specified the first page of results will be returned with a maximum count of 1,000 results per page. This helps ensure consistent and reliable performance regardless of the total result count.
All API endpoints returning a list of objects now provide metadata regarding the total count of results and pagination. For reference lists, returned from the /api/v1.0/administrative-units, /api/v1.0/features, /api/v1.0/glossary and /api/v1.0/counties endpoints, this means that results are now nested in a results property.
The places property of the placeList object has been renamed to results. This provides better consistency with other list object types.

Other changes:

API v0.9, as a prerelease API version, is now deprecated and will be removed on September 1st, 2020.

Improved accuracy of geographic queries, particulary in respect of coordinates associated with street names.
URI strings in Image and Audio objects are now properly escaped.

Page and PerPage query parameters to facilitate pagination of place result sets.
TotalPages, CurrentPage and CountPerPage properties to the placeList result object, to be displayed when the result set is paginated.
Additional descriptive error messages related to pagination (e.g. for index out of range-type errors).

Updated documentation and data dictionary to reflect the above additions.
Both 400 and 404 errors now return descriptive error messages in JSON format in addition to the appropriate HTTP status codes.