Introduction
In order to leverage the capabilities of the borderless™ widget, authentication is required through a dedicated endpoint. This process ensures the secure retrieval of a unique widget identifier. The obtained widgetId, serving as this unique identifier, will subsequently be utilized in constructing the widget URL, as exemplified in the borderless™ Link™ Recipes.
Please note that the widgetId holds validity for a duration of 15 minutes. Following expiration, a regeneration of the widgetId is necessary for uninterrupted widget access. For further details and implementation guidelines, refer to the provided examples in the borderless™ Link™ Recipes.
We appreciate your commitment to secure and streamlined interactions with the borderless™ widget. If you encounter any queries during the authentication process, our support team is available to assist you.
Data Requirements
Provide the following data requirements when sending a POST request to the Widget Authentication endpoint.
The body of the request should contain a JSON object with the the following information:
| Parameter | Required? | Description | Type |
|---|---|---|---|
| issuer | Yes | The 25 character alphanumeric string that is unique to your borderless™ Account and can be revealed in the Issuer ID column on the "Tokens" tab of your Developer Dashboard. An example would look like this: al2gyjp2bqqkm1598ekv9etfd | String |
| secretKey | Yes | The 36 character string that is unique to your borderless™ Account and is generated from the "Tokens" tab of your Developer Dashboard. An example would look like this: 42f1828e-c705-11ec-9d64-0242ac120002. | String |
| partnerKey | No | The 36 character string that is unique to your borderless™ Partner Account. This field is required when you want to use various different endpoints on behalf of your Child Accounts. | String |