Before you set up your Web integration, you must enable
localStorage within your WebView and keep it enabled. Set these parameters (or the equivalent parameters in your WebView provider):
domStorageEnabledmust be set to
incognitomust be set to
If your security policy limits outgoing traffic, ensure that your conditions allow for API calls by whitelisting all outgoing traffic from Link. These two content sources must be included at minimum:
<meta http-equiv="Content-Security-Policy" content="connect-src https://*.argyle.com; worker-src 'self' blob: "/>
To set up a web integration, include the Argyle Link initialization
html in your application's configuration.
You can copy-paste this initialization example into an
html file, then replace
YOUR_LINK_KEY with your own
linkKey to run Link. Find your Link key in the API keys section of the Argyle Console.
apiHostin this initialization example is set to the Argyle Sandbox API (
<https://api-sandbox.argyle.com/v1>). It's a good idea to test your implementation in Sandbox mode first, then change this to the Production API (
<https://api.argyle.com/v1>) when you are ready to go live.
Normally, the user closes Link but you can also close it by calling the
close method of the Link instance returned by
Argyle Link provides multiple configuration options and callbacks that customize how this UI element functions in your application. The only argument that is mandatory when invoking Argyle Link is the
linkKey, which you can find in the Argyle Console.
By default, anytime Argyle Link is initialized, it will be treated as a new session for a new user. To ensure your users retain their previous state in Argyle Link when it is re-initialized for them, your application must use the
For a full list of Link configuration parameters, see the Link reference.
User tokens are temporary access keys that let you start Argyle Link for an existing user.
Tokens are short-lived. Generate a new token using the API every time you initialize Argyle Link for a returning user.
You can create user tokens using the
Make sure that you request user tokens on your server-side and your
client_secret are never exposed on the front-end.
For a full list of callbacks, see the Link reference.
Link for Web updates automatically with each release. You do not need to take any steps to upgrade your Web integration.
Updated about 1 month ago