cdhs-trails-hotline-genesys-eapi

1.0.x
(0 reviews)

Purpose

The cdhs-trails-hotline-genesys-eapi Experience API provides and interface for inserting and updating Hotline call metadata records within the TRAILS database.

URLs

Sandbox: https://test-api.state.co.us/ext-dev-cdhs-trails-hotline-genesys-eapi/api/ping
QA: https://test-api.state.co.us/ext-qa-cdhs-trails-hotline-genesys-eapi/api/ping
Production: https://api.state.co.us/ext-cdhs-trails-hotline-genesys-eapi/api/ping

Headers

This system API requires a Client Id and Client Secret to be passed through the Headers of requests.

client_id: XXXXXX
client_secret: XXXXXX

Example Request

Each of the following examples assumes that you have the Headers configured as described in the Headers section above.

URL

External Dedicated Load Balancer

https://test-api.state.co.us/ext-dev-cdhs-trails-hotline-genesys-eapi/api/metadata/calls

Internal Dedicated Load Balancer

https://int-test-api.oit.colorado.lcl/ext-dev-cdhs-trails-hotline-genesys-eapi/api/metadata/calls

Full HTTPS Request / Code

External Dedicated Load Balancer

POST /ext-dev-cdhs-trails-hotline-genesys-eapi/api/metadata/calls HTTP/1.1
Host: test-api.state.co.us
client_id: XXXXXX
client_secret: XXXXXX

Internal Dedicated Load Balancer

POST /ext-dev-cdhs-trails-hotline-genesys-eapi/api/metadata/calls HTTP/1.1
Host: int-test-api.oit.colorado.lcl
client_id: XXXXXX
client_secret: XXXXXX

Reviews