Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.

Skip to main content

Create an individual onboarding link

There are two methods you can use to create individual onboarding links.

  • Run an API mutation to create a unique onboarding link for each future individual account holder.
  • Use a public URL from your Dashboard to share the same individual onboarding link with all of your users.
Public onboarding links

Use public links with caution. Those with fraudulent intent can use these public links to complete multiple onboardings, and if this happens undetected, they'll have multiple accounts in your project.

Unique links using the API​

Create a unique individual onboarding link for each user with the API.

  1. Call the onboardIndividualAccountHolder mutation.
  2. Enter information for all required API fields for the account country, as noted in country requirements for individual accounts.
  3. Include optional fields as needed for your use case (such as accountName or redirectUrl).
  4. Add optional messages to the success payload, either for validation or in case of rejection.

Mutation​

Open in API Explorer
mutation CreateIndividualOnboarding {
onboardIndividualAccountHolder(
input: {
accountCountry: FRA
email: "malika.ngomao@mybrand.io"
employmentStatus: Employee
language: "fr"
monthlyIncome: Between3000And4500
residencyAddress: {
addressLine1: "123 avenue de Paris"
city: "Paris"
country: "FRA"
postalCode: "75000"
}
}
) {
... on OnboardIndividualAccountHolderSuccessPayload {
__typename
onboarding {
id
statusInfo {
status
}
}
}
... on ForbiddenRejection {
__typename
message
}
... on ValidationRejection {
__typename
message
}
}
}

Payload​

If you added validation or rejection messages, you'll see information such as the onboardingId as well as the current status Ongoing (Valid) in the success payload.

{
"data": {
"onboardIndividualAccountHolder": {
"__typename": "OnboardIndividualAccountHolderSuccessPayload",
"onboarding": {
"id": "ae06faf6-13b2-4e9e-891b-e78ecd5ca0e4",
"onboardingState": "Ongoing",
"statusInfo": {
"status": "Valid"
}
}
}
}
}

Public link using the Dashboard​

  1. On your Swan Dashboard, go to Settings > Onboarding.
  2. In the onboarding URLs section, toggle Public URLs to on.
  3. Notice the URLs that appear for individuals and companies for each account country.
Public URL availability

Anyone could create an account using the public URL, and all accounts created are charged to your project.

Screenshot of Swan Dashboard onboarding page with a callout of the onboarding ID