OAuth 2.0 scopes
Fractal ID uses OAuth 2.0 as its underlying protocol. This protocol relies on scopes to limit application's access to user information.
We have the following scopes available.
User basic scopes
Scope | Description |
| Email address or phone number of the user (whichever they chose during registration, where they provide one or the other) |
| (default scope) Anonymized unique user identifier. |
User KYC scopes
There are two types of user KYC scopes, the verification scope and information details scope. One type allows you to request the verification status (like verification.basic:read
), while the second type allows you to access the information provided during the onboarding (verification.basic.details:read
).
If you wish to see the information details scope and request that the user goes through a given KYC level verification, you must specify both scopes.
Level scopes
KYC level / add-on | Verification scope | Information details scope |
---|---|---|
|
|
|
|
|
|
|
|
|
Add-on scopes
Asking a user for the following scopes without the presence of a level scope (like the ones above) is unsupported, and will result in an unexpected user experience.
KYC level / add-on | Verification scope | Information details scope |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[DEPRECATED] |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Client scopes
These scopes can be used during the client credentials flow.
Scope | Description |
| Grants access to our statistics API |
Last updated