Silent login’s token exchange moves to the Partners API
partner-login-token is now published on https://public-api.etoro.com and needs its own scope, so a partner token can mint silent-login tokens only where that scope was granted.- Exchange the tid for a one-time token —
POST /api/v1/silent-login/partner-login-token, with the newetoro-public:partner:silent-login:writescope - Scopes — silent login no longer runs without a scope
- Silent login errors — the
401and403this call returns, and what each one means
Silent login from a native mobile app
New guidance for partners whose users start on a phone, where the cookie is easily lost between the initiate page and the verify URL.- From a native mobile app — keep the handshake in one browser session, which browser to open on iOS and Android, and why a custom URL scheme cannot be a silent-login callback
Clearer names for sign-in, keys, and account association
The start page now namescode, sub, the non-interactive token, and the silent-login one-time token separately. Account association comes before the non-interactive token, because x-sub-account-id is the subAccountId from that association. Registration still does not return a sub-account id.- Four names —
code,sub, NIT, and OTT - Associate the accounts —
subandexternalUserIdper path, and wheresubAccountIdcomes from - Issue a non-interactive token — which path already has an
x-sub-account-id
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,
403causes,5xxon sub-account create, and missing profile claims - Associate the accounts — what each response of
POST /api/v1/sub-accounts/me/accountsmeans, and readingexternalUserIdfrom theGET, 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/initiatewithclient_id,redirect_uri, andstate. Your page no longer calls the initiate endpoint itself, and your callback checks thestateit gets back.
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