DCKAP Integrator
Search…
API Access Keys
Token generation for Dynamic Calls
DCKAP Integrator supports dynamic calls from various systems to synchronize data on the go. (Read about Dynamic Pipes here.)
The URL that is copied from the Dynamic Pipe is called from a system in order to read or write data. This URL is in turn made up of API calls (written inside Flows), which communicate with the respective systems to fetch data.
For additional security purposes, DCKAP Integrator also sets authentication in place. One of two methods can be used for authentication:
Users can use one of the following authentication methods while making API calls
  • Token Authentication: The dynamic token generated with an expiry time by DCKAP Integrator
  • Basic Authentication: A user-name, password combination

Token Authentication

A dynamic token generated from the user account, to be shared with the other systems. Click on API Keys from the Account Menu. The Create New Token page opens.

Create New Token

Provide the following information to create a new account.
Field Name
Description
Token Name
Any name for the user to identify later
Days
Days of Expiry. The token will be expired after specified days.
Password
Your Account Password
  • Once generated, the user can copy and enter the token while triggering a Dynamic Call from various systems.
  • Users can now generate Access Tokens of smaller size (64 characters) in the API Keys Module.
  • Dynamic Calls: During dynamic calls, it is possible to authorize DCKAP Integrator by using access_token, jwt_token in headers/params.
Examples:
http://0.0.0.0:2020/v1/dynamic/listener/<id>?access_token=<token>
http://0.0.0.0:2020/v1/dynamic/listener/<id>?token=<jwt_token>
  • This token is given as part of the header information in the following format:
Key Value
Authorization Bearer {token}
access_token {token}
Setting days to 0 (zero), will set the token expiry to unlimited.

Basic Authentication

DCKAP Integrator also supports basic authentication for accessing the API. The caller has to provide the account username and password in the request header.