Dataloy API 2.10 Release Notes
1. March 2016
With great pleasure Dataloy presents API 2.10
Highlights of this Release:
Highlights of Dataloy API 2.10
Multiple versions of the API
From API version 2.10 its possible have multiple versions of Dataloy API deployed on an application server. New API functionalities can be utilized for certain clients while at the same time continue to use older API versions for other clients. This usage of the system can remain until all clients are tested and working with the latest Dataloy API version.The API version is specified in the URL. More information: Versioning.
Adjust Number of Fields to be Returned from a Request
The number of fields to be returned from a request can now be adjusted, for example, in the header of a request it can be specified what field/s (no limit) of a resource is/are needed. The fields not mentioned will be ignored. This reduces the overhead of data transferred and improve performance. More information: API documentation.
Filtering Improvements
- Unique key: A resource and sub-resource can be filtered for using a unique key.
- Filtering can be performed for NULL and NOT NULL.
- Fields previously not supporting filtering can now be filtering, i.e. all fields in the API can now be filtered.
- More information: Filtering
Improved Underlying System Architecture and Performance Improvements
System architecture and API performance have been improved.
Remarks on Main Resource
Remarks appear on all main resources, and no sub resources, by default. Its possible to show a remark for a specific sub resource by adding fields.
Other
- A various cost/revenue list has been included on all applicable resources.
- There has been a bug in some of the previous releases where vesselCode on Document had to be accessed by using the following path: Document\voyage\voyageHeader\vesselCode\vesselCode\vesselCode, this has been corrected to Document\voyage\voyageHeader\vesselCode\vesselCode