Credentials API

Credentials API

Purpose

The Devo Credentials API allows users to create, retrieve, rename, and delete tokens, as well as enable or disable them. 

If multiple data sources need to send data to different tables using the HTTP API endpoint, the Credentials API can be used to create a token for each table programmatically. By assigning a unique token to each table, data sources are restricted from sending data to tables they are not authorized to use.

API versions

Please note that newer versions of this API may include pure additions to it (such as new properties on resources returned from an action, accepting these resources with or without the property inbound to the server, or adding new resources or actions), or new appearance of properties within JSON structures because we assume that clients use forgiving, non-strict parsing on the JSON they receive from Devo.

New versions of the API will always be backwards compatible, using a never remove, only add strategy.

Swagger docs

Check the following Swagger UI pages to visualize and interact with this API. Select the proper one according to your region and start trying the API.

Authorize you API requests

Note that you need a valid Devo token to authorize your Credentials API requests. Learn how to generate it in this article.