Integrations
This is the section where you can manage third-party application connections. This page is specifically engineered to make it possible for third party apps to use the Vendisto Web API.
Last updated
This is the section where you can manage third-party application connections. This page is specifically engineered to make it possible for third party apps to use the Vendisto Web API.
Last updated
Integrations are created in the section Settings/Integrations
An Integration consists of Integration name, Integration id, Integration secret, bearer token and issued date.
The Integration name is used to assign a name to the application receiving access to Vendisto API.
The Integration id is used for authenticating to the Vendisto API. It is the alternative for user name in OAuth2. (still in development)
The Integration secret is used for authenticating to the Vendisto API. It is the alternative for user password in OAuth2. (still in development)
The Bearer token is used for authenticating to the Vendisto API assigning it to a "Authorization" or "x-api-key" request header. (currently used)
The token itself is with infinite lifespan.
The Issued date is used to clarify when a application has been created.
When a new connection to a third-party application is needed, an Integration must be created. Then, a token can be generated for that Integration which will be used to authenticate when making requests to the API. To authenticate when making request, you should include one of the headers mentioned in the example below and set it's value to - Bearer {token}.
You can use either Authorization OR x-api-key header in order to authenticate!
