To learn more about Tempo products, please visit our Help Center. For support, see our Support Portal.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Unable to render {include} The included page could not be found.

As of September 23, 2019, we are going to make changes to our REST API. These changes will be implemented to improve the security standard of the REST API communication when retrieving an authorization token from Tempo. This change only affects how to create and renew a machine-to-machine authorization token from the API “https://api.tempo.io/oauth/token”.


In our current version, Tempo allows the parameters to be passed as query parameters in the URL As this is a violation of best practices we will from September 23, 2019, and onwards only accept the parameters to by passed in the x-www-form-urlencoded body of the HTTP request sent to Tempo. 


Steps to perform:


You can retrieve the oauth token API by performing:


curl -X POST 'https://api.tempo.io/oauth/token/?grant_type=authorization_code&client_id={your_client_id}&client_secret={your_client_secret}&redirect_uri= {your_redirect_url}&code={your_code}


Replace with the following:


curl -X POST 

  https://api.tempo.io/oauth/token/ 

  -H 'Content-Type: application/x-www-form-urlencoded' 

  -H 'Host: api.tempo.io

  -d 'grant_type=authorization_code&client_id={your_client_id}&client_secret= {your_client_secret}&redirect_uri={your_redirect_url}&code={your_code}'


Our API documentation has already been updated accordingly. 


You can reach out to our Support team or me if you have any further questions or need additional assistance.

  • No labels