Scopes | Parallel Developer Documentation
Parallel Developer Documentation Legacy – v1.x
This is documentation for Parallel Developer Documentation Legacy – v1.x, which is no longer actively maintained.
For up-to-date documentation, see the latest version (Current – v2.x).
Version: Legacy – v1.x
When users are initially redirected to the Parallel Markets Authentication server, a scope parameter must be provided. This scope should be a space-delimited list of scopes that identify the resources that your application could access on the user's behalf. These values inform the consent screen that Parallel Markets displays to the user, and determine what API's the resulting token will have access to based on user consent.
Here is a list of all available scopes:
| Scope | Description |
|---|---|
profile |
This scope provides access to the Profile API and basic information about an individual or business. This scope should always be included since it is necessary to retrieve the basic details of the entity that has authenticated. |
accreditation_status |
This provides access to the [Accreditations API](https://developer.parallelmarkets.com/docs/1.x/server/accred... |
identity |
This scope provides access to the Identity API and detailed KYC/AML data, contact information, identity documents, and Taxpayer Identification Certification (W-9). |
blockchain |
This scope provides access to the Blockchain API and information about confirmed wallets and Parallel Identity (PID) Token ownership. |
Note
Ensure your customer account has been enabled for the accreditation_status or identity scopes before attempting to request them. If your account has not been authorized to request those scopes, the Authorization URL redirect will display an error.