Setup
| Time to Complete | 5 minutes |
|---|---|
| Skills Required | No technical skills! |
Complete this Setup guide before following the 1-Click Verify API Integration guide.
1. Access the Dashboard.
Create or log into your Verified Dashboard account.
How to Create a Dashboard Account
a. Enter your email and click the 1-Click Login button.
We'll send you a verification code by email.
Use your work email. We use AI to auto-magically set brand information based on your email domain, so you don't have to manually enter it!
b. Complete the verification step.
Click the verification button in the email or enter the verification code. We'll automatically log you in. It's a 1-click experience, as promised!
c. (optional) Set up MFA.
Set up multi-factor authentication with an authenticator app. This is optional until you request approval for Production access, at which point it's required.
d. (if necessary) Confirm your company name.
If you're creating the Dashboard account for your company, we'll ask you to confirm your company name. If someone on your team has already created your account, you won't need to do this.
If your account doesn't have a brand yet, we'll automatically create one for you and take you to its Brand Details page.
Your company account can have one or more brands. Generally, you'll only need one brand, but there are some cases where it's helpful to use multiple. For example:
- If you have multiple products: If you have products that go by different names, it can be useful to create different brands to help users know which product they're using 1-Click Signup for — and to help your team track metrics specific to that product.
- If you want to try different brand settings: If you want to change brand settings without affecting your existing implementation (even in Sandbox), you can duplicate your brand and configure different settings on the new brand.
e. (optional) Invite team members.
Invite your team members to join your Dashboard account.
2. Configure brand settings.
On the Brands page, click the Create button to create a new brand, or click Brand Details to access brand settings for an existing brand.
Brand Name
Choose an external name for your brand. This will be used elsewhere in the Dashboard (for example on the Metrics page) and displayed to users in the SDK (if you choose to use the SDK).
The internal brand name is separate, and you can edit it at the top of the page. You can use this to label brands created for testing purposes, for example.
1-Click Verify Settings
Channels
Choose which channel(s) you want to enable:
| Option | Description |
|---|---|
| Autofill Recommended | Autofill verified phone number with no user input |
| Silent Recommended | Autofill verified phone number with no user input |
| SMS Always Enabled | Verify phone number with SMS OTP |
The autofill channel lets you autofill a user's phone number with no user input — the best user experience on the planet! And the silent channel lets you verify a user inputted phone number without sending an SMS. But these channels don't yet work for all user sessions, so it's best to fall back from autofill to silent to SMS.
- Autofill and Silent: We bill per autofill/silent started (not succeeded), but you can use the
GET /1-click/verifications/channelsfor free to check in advance if autofill will succeeded. Almost 100% of the time, if this endpoint indicates the autofill channel is available, autofill will succeed. The only exceptions are rare edge cases, for example when a user loads the page on cell data but then switches to WiFi before starting autofill (since autofill doesn't yet work on WiFi). - SMS: We bill per SMS sent.
- All channels: We bill per verification succeeded.
Delivery Format
Configure a default delivery format for SMS verification messages.
Default Format
This setting determines a default value, which you can override anytime by including format in the request body of POST /1-click/verifications/{uuid}/deliver.
Choose a format for the SMS verification message:
| Option | format | Description | Template | Example |
|---|---|---|---|---|
| Code | "code" | A one-time code the user types in |
|
|
| Link | "link" | A one-time link the user clicks |
|
|
| Code and Link | "codeAndLink" | Both, with the code first |
|
|
| Link and Code | "linkAndCode" | Both, with the link first |
|
|
Redirect URL
This setting is only relevant if you use the link format with the SMS channel: that is, if you send SMS with verification links (instead of verification codes).
This setting determines a default value, which you can override anytime by including redirectUrl in the request body of POST /1-click/verifications/{uuid}/deliver.
Set a redirect URL, which is where 1-Click Verify redirects a user to. The redirect URL can be any valid URL — whether a website link, app store link, or otherwise.
Redirect User After
This setting is only relevant if you use the link format with the SMS channel: that is, if you send SMS with verification links (instead of verification codes).
This setting determines a default value, which you can override anytime by including redirectUserAfter in the request body of POST /1-click/verifications/{uuid}/deliver.
Choose when a user should be redirected:
| Option | redirectUserAfter | Description |
|---|---|---|
| 1-Click Verify | "phoneVerification" | After the 1-Click Verify flow (where we verify the user’s phone number) |
| Hosted 1-Click Signup/Health | "infoConfirmation" | After a 1-Click Signup and/or 1-Click health flow we host (where we autofill info and have the user confirm it) |
If you choose the "1-Click Verify" option, we will redirect the user after we verify their phone number. You can then optionally:
- Confirm the user's phone is verified.
- Pass the user to an integrated 1-Click Signup flow on your side.
See step 3 for how to do this.
If you've already integrated 1-Click Signup (following the SDK Integration or API Integration guide), the "Text to Signup" option is best, because it ensures you can keep your signup flow consistent for all users.
If you choose the "Hosted 1-Click Signup" option, we will take the user through a hosted 1-Click Signup flow that autofills identity info and has them confirm it. You'll need to retrieve the user's info to benefit from this: see step 3 for how.
You're done with this Setup guide! ✅
Now, follow the API Integration guide to integrate 1-Click Verify into your application.