Introduction
This API will allow the user to query for complete information on services. The API can be called without passing a ID parameter in the path to get a specific service. Please note that if you are searching for a list of locations and don’t need all the information the \locations call will be faster.
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
Info |
---|
Scope Needed For This API - mi-cie.hub/read
|
Rest URL
The following are the URLs for this API.
Environment | URL |
---|---|
UAT | GET https://directory-uat.mi-cie.org/v1/locations/complete/{id} GET https://directory-uat.mi-cie.org/v1/locations/complete/ |
Production | GET https://directory.mi-cie.org/v1/locations/complete/{id} GET https://directory.mi-cie.org/v1/locations/complete |
Swagger Definitions
The following are the URLs for this API.
Environment | URL |
---|---|
UAT | https://directory-uat.mi-cie.org/v1/swagger#/services/get_services_complete https://directory-uat.mi-cie.org/v1/swagger#/services/get_services_complete__serviceId_ |
Headers
The following will be headers that will need to be supplied
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 |
---|---|---|
Path Parameter | ||
| This will be the service id of the requested record in the directory. *Please note that this is only needed if you want to get a specific service payload for a ID. |
|
Query String | ||
| A query parameter that will filter out the locations that will be returned. This is an json object and The following lists commonly used query strings used for this API https://brightstreetgroup.atlassian.net/wiki/spaces/CIEP/pages/1576763393/services#Common-Queries |
|
| This will be which page of data that the user wants to be returned. | Default to Page 1 |
| This will be the number of records that can be queried at a time. The maximum that can be queried is 30. | 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. https://tools.ietf.org/html/rfc7807 .
HTTP Status Code | Description | Response Example | ||
---|---|---|---|---|
200 | Successful call with no service matching the query passed in. |
| ||
200 | Successful retrieval of a service complete record.
|
| ||
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 |
| ||
401 | Unauthorized |
| ||
502 | Bad Gateway. Our API services maybe down |
|
Example CURL for this API Call
The following is an example CURL for calling this api.
Code Block |
---|
curl -v
--request GET 'https://directory-uat.mi-cie.org/v1/locations/complete'
--header 'x-api-key: aGZoczo4****2ZDk='
--header 'Content-Type: application/json'
--header 'Authorization: bearer etty****iquerui'
|