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

# Introduction

> Welcome to the eToro Partners API

The eToro Partners API lets approved partners onboard and manage end users on eToro. Where the [Core API](/) covers trading and market data for your own account, the Partners API covers the lifecycle around a user: registering them, taking them through KYC and verification, opening accounts, and moving money.

<Note>
  Access to the Partners API is granted per partner. If you are not yet onboarded as an eToro partner, contact your eToro representative — these endpoints are not available with standard API keys.
</Note>

## What you can build

<CardGroup cols={2}>
  <Card title="User registration" icon="user-plus">
    Register new eToro users on behalf of your platform, and check registration eligibility before you start.
  </Card>

  <Card title="KYC & verification" icon="clipboard-check">
    Drive the full KYC flow — questionnaires, required fields, document upload, screening, and electronic verification.
  </Card>

  <Card title="Accounts" icon="wallet">
    Create and inspect cash accounts and sub-accounts, and check creation eligibility and status.
  </Card>

  <Card title="Money movement" icon="arrow-right-arrow-left">
    Handle first-time deposits, crypto deposit intents, and crypto withdrawals for your users.
  </Card>
</CardGroup>

## Authentication

The Partners API uses the same authentication as the rest of the eToro Public API. Every request is authenticated one of two ways:

* **API key pair** — send both `x-api-key` (identifies your application) and `x-user-key` (identifies the user) headers. The two are always sent together.
* **OAuth 2.0** — a bearer token obtained through the authorization code flow, scoped to the operations you need (for example `etoro-public:kyc:write` or `etoro-public:money.accounts:read`).

The two methods are alternatives — never send a bearer token alongside the key pair. Each endpoint in the reference lists the scopes it requires.

<Card title="Authentication guide" icon="key" href="/core/getting-started/authentication">
  How to generate keys and format your request headers.
</Card>

## Base URL

All Partners API endpoints are served from:

```
https://public-api.etoro.com
```

## Next steps

<CardGroup cols={2}>
  <Card title="API Reference" icon="code" href="/partners-api-reference">
    Browse every Partners API endpoint, grouped by capability.
  </Card>

  <Card title="Changelog" icon="clock-rotate-left" href="/partners/changelog">
    New endpoints and breaking changes in the Partners API.
  </Card>
</CardGroup>