Endpoints
Postman API documentation is available at https://api.docs.verified.inc.
Please do all development work and testing against our Sandbox environment, which returns mock data. You can use our Production environment when you're ready to go live.
1-Click Signup
POST /client/1-click
Create a (one time use) session key for the client SDK
| Method | POST |
|---|---|
| Path | /client/1-click |
This endpoint is only relevant if your brand's integration type setting is set to SDK in the Dashboard. See Integration Type in the Setup guide for more information about integration types.
Request
{
phone?: string
}
| Property | Required? | Type | Format | Default | Description | Example |
|---|---|---|---|---|---|---|
phone | optional | string | E.164 | none | User's phone number (in E.164 format) | "+12125550010" |
If you don't have a user's phone number yet, call POST /client/1-click with an empty request body, and the SDK will prompt the user to enter their phone number.
Response
{
sessionKey: string
}
| Property | Type | Format | Description | Example |
|---|---|---|---|---|
sessionKey | string | Version 4 UUID | Session key that can be used (one time only) to initialize the SDK | "86227634-bd2e-479d-9541-2c8e7e2e1f6d" |
GET /1-click
Get data for a user who has completed a 1-Click Signup flow
| Method | GET |
|---|---|
| Path | /1-click/{identityUuid} |
Request
Call:
GET /1-click/{identityUuid}
- For the
{identityUuid}path parameter, use the value of theidentityUuidreturned by the SDK or included as a URL parameter on the redirect URL.
Response
{
...1ClickEntity
}
See 1ClickEntity.
POST /1-click
Begin a 1-Click Signup flow
| Method | POST |
|---|---|
| Path | /1-click |
This endpoint is only relevant if your brand's integration type setting is set to API in the Dashboard. See Integration Type in the Setup guide for more information about integration types.
Request
{
phone: string,
email?: string,
birthDate?: string,
ssn4?: string,
fullName?: {
firstName?: string,
middleName?: string,
lastName?: string
},
address?: {
line1?: string,
line2?: string,
city?: string,
state?: string,
zipCode?: string,
country?: string
}
credentialRequests?: CredentialRequest[]
}
| Property | Required? | Type | Format | Default | Description | Example |
|---|---|---|---|---|---|---|
phone | required | string | E.164 | none | User's phone number (in E.164 format) | "+12125550010" |
email | optional | string | none | User's email address | "richard@piedpiper.net" | |
birthDate | optional | string | YYYY-MM-DD | none | User's birth date (in Sandbox, this must be "1989-08-01" to pass validation) | "1989-08-01" |
ssn4 | optional | string | 4 digits (0-9) | none | Last 4 digits of user's Social Security Number (in Sandbox, this must be "6789" to pass validation) | "6789" |
fullName | optional | Object | Object with keys for one or more child credentials listed below | none | Full name | |
↳ fullName.firstName | optional | string | cAse inSensiTive | none | First name | "Richard" |
↳ fullName.middleName | optional | string | cAse inSensiTive | none | Middle name | "Harrison" |
↳ fullName.lastName | optional | string | cAse inSensiTive | none | Last name | "Hendricks" |
address | optional | Object | Object with keys for one or more child credentials listed below | none | Address | |
↳ address.line1 | optional | string | cAse inSensiTive | Line 1 of address | "5320 Newell Rd" | |
↳ address.line2 | optional | string | cAse inSensiTive | Line 2 of address | "" | |
↳ address.city | optional | string | cAse inSensiTive | City of address | "Palo Alto" | |
↳ address.state | optional | string |
| none | State of address |
|
↳ address.zipCode | optional | string | none | ZIP Code of address |
| |
↳ address.country | optional | string |
| Country of address |
| |
credentialRequests | optional | CredentialRequest[] | See CredentialRequest | Defined by the default credential requests brand setting in your Dashboard | List of CredentialRequest objects (which encode which credentials you're asking for) | See CredentialRequest example |
Default Credential Requests
If you don't include credentialRequests in the request body, the default credential requests setting for your brand will apply. For reference, the standard credential requests (see here in the Setup guide) include the core KYC data points, all set to optional:
Standard Credential Requests in Code
[
{
"type": "FullNameCredential",
"children": [
{
"type": "FirstNameCredential"
},
{
"type": "MiddleNameCredential"
},
{
"type": "LastNameCredential"
}
]
},
{
"type": "PhoneCredential"
},
{
"type": "AddressCredential",
"multi": true,
"children": [
{
"type": "Line1Credential"
},
{
"type": "Line2Credential"
},
{
"type": "CityCredential"
},
{
"type": "StateCredential"
},
{
"type": "ZipCodeCredential"
},
{
"type": "CountryCredential"
}
]
},
{
"type": "BirthDateCredential",
},
{
"type": "SsnCredential",
}
]
Response
{
uuid: string,
identity: 1ClickEntity
}
| Property | Type | Format | Description | Example |
|---|---|---|---|---|
uuid | string | Version 4 UUID | Unique identifier for the 1ClickEntity that will be returned at the end of the 1-Click Signup flow | "535dba63-d4bd-442a-b3f6-21b785260a08" |
identity | 1ClickEntity | See 1ClickEntity | A 1ClickEntity object, which contains the user's verified data and metadata about it | See 1ClickEntity example |
Verification
GET /1-click/verifications
Check the status of a verification flow
| Method | GET |
|---|---|
| Path | /1-click/verifications/{verificationUuid} |
Request
Call:
GET /1-click/verifications/{verificationUuid}
- For the
{verificationUuid}path parameter, use the value of theverificationUuidincluded as a URL parameter on the redirect URL.
Response
{
...1ClickVerificationEntity
}