Legacy Accounts
List the authenticated user's legacy accounts, grouped by loginid.
Temporary endpoint
Endpoint
/trading/v1/options/legacy/accountsBase URL: https://api.derivws.com
Status Codes
Error Responses
{
"errors": [
{
"status": 404,
"code": "NotFound",
"message": "User has no legacy account mapping"
}
],
"meta": {
"endpoint": "/trading/v1/options/legacy/accounts",
"method": "GET",
"timing": 16
}
}{
"errors": [
{
"status": 409,
"code": "MigrationPending",
"message": "User migration is pending or has failed"
}
],
"meta": {
"endpoint": "/trading/v1/options/legacy/accounts",
"method": "GET",
"timing": 19
}
}Authentication Required
Deriv-App-ID header to identify your application, plus a valid OAuth2 Bearer token. OAuth2 Scope: tradeAbout Legacy Accounts
The GET /trading/v1/options/legacy/accounts endpoint: List the authenticated user's legacy accounts, grouped by loginid.
Response Shape
The response contains a loginids map where each key is a Deriv loginid (e.g. CR90000123) and the value is an array of legacy account objects associated with that loginid.
No Legacy Mapping
A 404 response indicates the authenticated user has no corresponding accounts on the legacy options platform. This is expected for users who signed up after the platform migration.
Migration Conflict
A 409 Conflict response means the user's migration is currently in progress or has failed. Check the migration-status endpoint to determine the exact state.
Any other questions? Get in touch