The Update API is used to get updates to practitioners previously returned to a Client through the Search API that have been updated since a given date / time value.
Root/Version/Request&Security
Within that structure, this section documents how the Request portion is used for update requests. The following points are relevant to structuring update requests:
The Request portion of an update request consists of the command, three required parameters, and two optional parameters: Command/Index?Time&Type&Page Size&Page Number
Command = update
Required:
Index - Names the index used for updates. Currently, use masterfile for all queries.Time - An ISO formatted date string indicating the date / time after which updates will result in a return (e.g., time=2000-05-29T16:24:08.412Z).Type - Indicates the type of return values. Either full or ids.
type=full indicates that full practitioner data for changed records should be returned.
type=ids indicates that only ids for changed records should be returned.Optional:
Page Size - Defines the number of returns per page. Default = 10. Max. = 250.
pageSize=n
pageSize=20
Page Number - Specifies the page to return. If not specified, returns the first page of results.
page=n
page=3 - Returns the 3rd page of results.Any parameters after the first must be separated by an ampersand (&). An ampersand (&) must precede the Security portion of the URL.
The following URL would return the first page of full records updated since the date / time given, with a page size of 20 records per page:
https://api.hmsonline.com/v1/update/masterfile?time=2000-05-29T16:24:08.412Z&pageSize=20&page=1&type=full×tamp=1369844777731&key=EU2BD6eHBQeUMpMxDW9dmg==&signature=8qrFmQbQgILzdDeQfbJTxHXeZvE=
Note: All security values shown here and throughout this documentation are for illustration purposes only and will not work as shown. See Security Credentials for more information.