One API application, one token endpoint, three headers on every call.
PerspioTalk APIs authenticate integrations with the OAuth 2.0 client credentials grant. Each integration has its own API application in your Perspio tenant. The application's client ID and secret get you a short-lived access token. You then send that token, your tenant ID and your subscription key with every request.
What you need
| Value | Where it comes from | Used for |
|---|---|---|
client_id | Your API application | Requesting a token |
client_secret | Your API application (shown once, when created) | Requesting a token |
Ocp-Apim-Subscription-Key | Your API application | Every API call |
tid | Your API application | Every API call |
access_token | The token endpoint | Every API call, as Authorization: Bearer |
Steps
- Create Application. A Perspio administrator creates an API application for your integration and records its credentials.
- Get Access Token. Exchange the client ID and secret for a bearer token, then call any PerspioTalk API with it.
What an integration can access
An API application's access and permissions are set when an administrator creates it in Perspio, and they apply to every token it receives. To change what an integration can do, update its API application in Perspio.
Replacing the earlier sign-in flowsEarlier versions of these docs described Microsoft Entra ID sign-in: tokens from
login.microsoftonline.com,api://perspiotalkscopes, API users, the authorization code flow and refresh tokens. The token endpoint on Get Access Token replaces all of them. Move any integration that still requests tokens fromlogin.microsoftonline.comto it.