Link Errors

This page provides common causes and troubleshooting suggestions for these Link errors:

• invalid_link_items
• invalid_pd_config
• invalid_link_key
• invalid_user_token
• generic

All errors (except generic) occur due to invalid Link configuration and are not expected to reach the production environment.

Link errors are returned with onError callback function.

The function will be passed the type of the error that occurred.

This page does not exist. Reach out to [Company name] for help.

N/A

• The user was deep linked to a Link item that does not exist (see Deep linking for additional information).

• A constrained list of Link items was provided in the Link configuration, but all of the provided Link items do not exist.

Check if the Link item is available by calling GET /link-items/:id endpoint each time before initializing Link when deep linking or constraining a Link item list.

In the case where you are keeping a map of available Link items on the backend, occasionally call GET /link-items endpoint to sync the newest updates.

The service is experiencing connection problems. Please try again later.

Reason: invalid PD config.

The pay distribution config provided when initializing Link is invalid.

• Check the configuration parameters of the provided pay distribution config (see Pay distribution configuration for additional information).
• Check that the pay distribution config is encrypted correctly using the Argyle encryption endpoint (see Link integration for additional information).

Please make sure your linkKey is correct.

N/A

The Link key used when initializing Link is invalid.

Check if you are using an appropriate Link key for the selected environment. There are separate Link keys for the sandbox and production environment. Link keys can be found in the API keys section of the Argyle Console.

The service is experiencing connection problems. Please try again later.

Reason: invalid userToken.

User token provided during Link initialization is not a valid JWT token and could not be decoded.

• Check if the used userToken is the same provided by /user-tokens endpoint or via onUserCreated callback (see Callbacks for additional information).
• Check if the user token is not modified (e.g. additionally encoded) before being passed to Argyle during Link initialization.

N/A

Something unexpected happened. Argyle is investigating.

Please contact our support team for more details.