> ## Documentation Index
> Fetch the complete documentation index at: https://docs.whitebit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# OAuth 2.0 on WhiteBIT

> OAuth 2.0 integration with WhiteBIT enables secure, token-based authorization for third-party applications.

## Key Benefits

* **Enhanced Security**: Users grant access without sharing WhiteBIT credentials with third-party applications
* **Granular Permissions**: Fine-grained scope controls allow users to limit what third-party applications can access
* **Streamlined Trading Experience**: Enables seamless integration with portfolio trackers, trading bots, and analysis tools
* **Developer-Friendly**: Standardized implementation familiar to developers across the ecosystem

## How WhiteBIT OAuth Works

<Steps>
  <Step title="Authorization">
    Users approve access for a third-party application through WhiteBIT’s authorization page
  </Step>

  <Step title="Token Exchange">
    The application exchanges the authorization code for an access token
  </Step>

  <Step title="API Access">
    The application uses the access token to make API calls to WhiteBIT on the user’s behalf
  </Step>

  <Step title="Token Refresh">
    When the access token expires, the application can use a refresh token to obtain a new one
  </Step>
</Steps>

## Use Cases

#### Partner API key issuance

Partner platforms issue WhiteBIT API keys on behalf of end users through the OAuth API key flow. The flow replaces manual key creation with a consent-driven bootstrap: the user authorizes the partner once, and the WhiteBIT platform issues a partner-scoped API key with a secret that the partner retrieves through a dedicated endpoint. See the [Fast API Key integration guide](/guides/fast-api-key-via-oauth).

#### Trading Bots & Algorithmic Trading

Enable automated trading strategies without storing WhiteBIT credentials in third-party systems. Trading bots can place, modify, and cancel orders while only having the specific permissions they need.

### Portfolio Trackers & Analytics

Allow portfolio management applications to read balance and trade history information without write access to trading functions, providing users with consolidated views of their assets across multiple platforms.

### Mobile Applications

Provide a seamless authentication experience in mobile apps without requiring users to enter and store their WhiteBIT credentials in the app.

### Enterprise Integrations

Enable business systems to securely connect to WhiteBIT for institutional trading, reporting, and compliance purposes with proper audit controls.

## Available Scopes

WhiteBIT OAuth 2.0 implementation supports a wide range of permission scopes available for request during client setup, including:

* Account information access
* Balance and transaction history
* Order management (read, create, delete)
* Market data access
* Trading history
* OAuth API key management (`apikeys.create`, `apikeys.read`, `apikeys.delete`)
* And more specialized permissions

For a complete list of available scopes and detailed implementation instructions, please visit the [Usage](/platform/oauth/usage/overview#scopes) page.

## Getting Started

**WhiteBIT OAuth 2.0 integration is exclusively offered to close ecosystem partners.** To integrate WhiteBIT OAuth 2.0 with an application, contact support at [support@whitebit.com](mailto:support@whitebit.com). The support team guides through the OAuth integration process, including:

1. Application registration and approval
2. Scope request and configuration
3. Implementation support for the OAuth 2.0 authorization flow
4. Technical documentation for token exchange and API authentication

Once the integration request is approved, detailed instructions are provided for implementing the OAuth 2.0 flow.

## Next Steps: Implementation Details

The [Usage](/platform/oauth/usage/overview) page provides comprehensive documentation on:

* Endpoint specifications for authorization and token exchange
* Request and response formats with example code
* Complete list of available scopes and their permissions
* Step-by-step implementation guides for common scenarios
* Troubleshooting tips and best practices

The usage documentation guides through the entire implementation process from initial setup to making the first authenticated API calls. For partner integrations that need to issue API keys on behalf of users, the [Fast API Key integration guide](/guides/fast-api-key-via-oauth) covers the end-to-end consent and key-management flow. The [OAuth endpoint overview](/api-reference/oauth/usage/overview) lists every OAuth endpoint in the API Reference.

## Support

For questions or assistance with OAuth 2.0 integration, contact support at [support@whitebit.com](mailto:support@whitebit.com).