GET \services\changes

Introduction

This API will allow the use to query for header information on services. This API will return identifiers of services that have been modified, added, or deleted during a time period.

Authorization

The authorization will contain an API key and also will use an OAuth2 access token. An API key will be provided to each client that intends to consume this API. A development key and also a separate production key will be provided. If this key is not included then an authorization error will be returned.

The process for getting an OAuth2 token can be found here Authorization

Scope Needed For This API - mi-cie.hub/read

Rest URL

The following are the URLs for this API.

Environment	URL

Environment

URL

UAT

GET https://directory-uat.mi-cie.org/v1/services/changes

Production

GET https://directory.mi-cie.org/v1/services/changes

Headers

The following will be headers that will need to be supplied

Header	Description

Header	Description
x-api-key	This will be a key that will provided by a community information exchange administrator.
ContentType	application/json
Authorization	This will be the access token that was retrieved using your client id and secret

Request

Note that the person ID passed as a parameter in the URL as documented in the REST URL section.

Data Element	Description	Default

Data Element	Description	Default
Query String
`startDateTime`	This will be the start date and time in which modifications, additions or delegations. The following is a example format `2023-06-15T13:45:30`	Required Field
`endDateTime`	This is the end date and time. If this parameter is not passed in then the current date and time of the call will be used. `2023-06-15T13:45:30`	Current Date and Time of Call.
`page`	This will be which page of data that the user wants to be returned.	Default to Page 1
`per_page`	This will be the number of records that can be queried at a time. The maximum that can be queried is 100.	Default to 10

Response

The following will be the response values from the calling of the API. The error responses will conform ]to the following specification. RFC 7807: Problem Details for HTTP APIs .

HTTP Status Code	Description	Response Example

HTTP Status Code	Description	Response Example
200	Successful retrieval of a service record.	`[ { "serviceId": 1, "modifiedDateTime": "2023-06-15T13:45:30", "modification": "UPDATE" }, { "serviceId": 2, "modifiedDateTime": "2023-06-15T13:45:30", "modification": "CREATE" }, { "serviceId": 3, "modifiedDateTime": "2023-06-15T13:45:30", "modification": "DELETE" }, ]`
403	Request is unauthorized and will not be processed. This will happen if the authorization header does not contain a valid client id and secret.
400	Request is malformed and will not be processed.
500	Internal Server Error

Example CURL for this API Call

The following is an example CURL for calling this api.