Skip to main content
What changed in the etoro Partners API, newest first. Each entry lists the API version the change shipped in, so you can line it up against the version shown in the Partners API reference. The Partners API versions independently of the Core API, which has its own changelog.
​
Docs
Docs

​
Troubleshooting for partner sign-in and account association

Partners can now look up the errors they meet while connecting an etoro user, with the cause and the next step for each.
  • Troubleshooting — sign-in failures during testing, 403 causes, 5xx on sub-account create, and missing profile claims
  • Associate the accounts — what each response of POST /api/v1/sub-accounts/me/accounts means, and reading externalUserId from the GET, because the create response does not include it
  • Identity and personal data — storing sub, and why there is no display name by default

​
Silent login starts on etoro’s initiate page

  • Send the browser to etoro’s initiate page — open https://www.etoro.com/accounts/partners/silent-login/initiate with client_id, redirect_uri, and state. Your page no longer calls the initiate endpoint itself, and your callback checks the state it gets back.
​
Docs
Docs

​
Events from etoro

Partners that consume outbound account events can now follow the delivery contract and message schema for the Azure Event Hub etoro publishes to.
  • Events from etoro — Event Hub delivery, envelope, and operational rules
  • KYC — payload and field names for the KycUpdates event
​
Money
v1.387.0

​
Check crypto deposit eligibility

You can now query whether an account is eligible to deposit crypto.
  • GET /api/v1/money/deposit/crypto/eligibility — crypto deposit eligibility
​
Docs
v1.326.0

​
The Partners API reference is published

The Partners API now has its own reference section, generated from the same pipeline as the Core API and versioned independently of it.Entries here cover the Partners API only. Changes to the Core API stay in the Core API changelog.