Download SPOR API Documentation
The latest version of the API specification incorporates the following additional information:
- A description of how an implementing system must retain rowid elements in the creation, and later management, of change requests in RMS.
- A description on the fields that have to be conditionally provided when dealing with both OMS and RMS change requests depending on the status and the data of such requests.
- An explanation on how OMS retains compatibility for searching elements based on identifiers, even after they have been merged, and how the current identifier, of an element, is highlighted in the response data.
- A description on what kind of change requests can be filed in OMS depending on the status of the referred organisation and/or location.
Please note that in the SPOR API specification, the services are set out in Section 6 and those that are OMS-specific are marked “O”, RMS-specific are marked “R”, and services shared by both RMS and OMS are marked as “RO”.
The documents have been shared with the SPOR Task Force and UAT testers.