
Customer Authentication API: This API is developed by you and is responsible for generating signed tokens for callstats authentication.
Callstats Authentication API: auth.callstats.io. For further instructions see docs.callstats.io.
Callstats REST API: Depending on payload either stats.callstats.io or events.callstats.io e.g.User Action Events. For further instructions see docs.callstats.io.
3 - Once your App gets a valid token from your Customer Authentication API it can send an access request to Callstats Authentication API by passing the following parameters:
grant_type string Required Must be set to "authorization_code"4. Callstats Authentication API returns an access token to your App. Your App is now able to send any request to Callstats REST API.
code string Required JWT signed ApplicationToken with alg set to ES256 (this is the signed token returned on Step 2 above)
client_id string Required localID@appID ( localID is provided by the developer and MUST NOT be null or empty)
A successful response from Callstats Authentication API is something like:
{
"access_token":"-064b-4a76-8a2d-d686ec773992", "expires_in":3600,
"token_type": "bearer"
}
5. Your App can now send any request to Callstats REST API by including the access token in the authorization header.
POST /token HTTP/1.1 Host: server.example.com Authorization: Bearer czZCaGRSa3F0MzpnWDFmQmF0M2JW Content-Type: application/json;charset=UTF-8
Comments
0 comments
Please sign in to leave a comment.