Pinwheel Link is a front-end modal that allows users to search for their employers and payroll providers and seamlessly authenticate with their payroll platform credentials in order to authorize access to their payroll account.
There are several methods for implementing Pinwheel Link. For web application you can embed Pinwheel Link directly into your site. For mobile development we recommend using one of our [Link SDKs](🔗): React Native, Android, and iOS.
We understand how important it is to have a cohesive user experience, so we’ve made Pinwheel Link highly customizable. All customizations are done via Link token creation. Some of the most notable customizations include:
Skipping the Pinwheel intro screen.
Building your own search functionality.
Disabling partial direct deposit switch.
For more information on navigating these customizations please take a look at our [Implementation Guide](🔗).
# Link Tokens
In order to initialize Pinwheel Link, your server side code will need to generate a short-lived Link token by sending a POST request to the [/link_tokens](🔗) endpoint. Link tokens are intended to be single-use and expire after 15 minutes. Your server should generate a new Link token each time you wish to launch Pinwheel Link.
**Do not** ever send this request from the client side and publicly expose your API Secret.
id` returned here is identical to the `
link_token_id` included with [webhooks](🔗), and should be stored accordingly. You can find recommendations for storing identifiers [here](🔗)
# Link Events
Link events are returned to your client and will give you visibility into what is happening in the modal as the user moves through Pinwheel Link. The nine different event types are outlined below. It is up to you to determine how to use these events for tracking.
|`||Modal was opened||`|
|`||User selected an employer||`|
|`||User selected a platform||`|
|`||Client has incorrect platform in token||`|
|`||User has submitted login attempt for the first time||`|
|`||User logged in successfully||`|
|`||User inputted an amount||`|
|`||Modal was exited||`|
|`||User reached the success screen. For direct deposit jobs, this will occur when the job has completed successfully. For all other jobs this will be when the user logs in successfully, as these jobs are completed in the background.||`|
|`||User was shown an error||`|
For On Demand Updates, the `
select_platform`, and `
incorrect_platform_given` events are not sent since the `
account_id` is already associated with a platform. Additionally, the `
login_attempt` event is only sent if user input is required and an attempt to login is made.
You can find more detail on Link errors and error handling [here](🔗).
# Reference Types
The following types should be used while integrating Link into your application.
The boolean `
pendingRetry` is `
true` when the job results in an error but will be retried asynchronously. Your user will be notified that their request is pending. This is available starting Link v2.3 and above.
|`||The Link token created using the [/link_tokens](🔗) endpoint.|
|`||Callback whenever a user successfully logs in to their payroll account.|
|`||Callback whenever a user reaches the success screen. For direct deposit jobs, this will occur when the job has completed successfully. For Income and Employment jobs this will be when the user logs in successfully, as these jobs are completed in the background.|
|`||Callback anytime an error occurs during the flow. This could be a user error like incorrect credentials or a system error. Receiving this callback does not necessarily mean the flow cannot proceed.|
|`||Callback whenever a user exits the modal either explicitly or if an error occurred that crashed the modal.|
|`||Callback with more granular events to help you track usage. All possible events are listed [here](🔗).|
Please contact [[email protected]](🔗) for access to our [Developer Dashboard](🔗).