Maryia/feat: Remove demo signup from legacy-api website

[maryia-deriv]

1. Remove demo signup from legacy-api website at /api-explorer/#new_account_virtual.

File	Change
static/data/v3.yml	Removed the new_account_virtual / New Virtual-Money Account entry from the dropdown list
config/v3/new_account_virtual/	Deleted the entire directory (send.json, receive.json, example.json)
src/configs/websocket/api.calls.types.ts	Removed the two NewVirtualMoneyAccountRequest/Response imports and the new_account_virtual type mapping block
i18n/fr/.../setting-up-a-deriv-application.md	Removed the new_account_virtual API link from the French docs, keeping the sentence grammatically correct

2. Content update on Home page:

• All-new -> Legacy API retirement
• Build with the new Deriv API -> Legacy API is being retired. Move to the new Deriv API.
• It's faster to integrate, comes with OAuth 2.0 authentication, and built around how developers actually work. Legacy API remains available as the same old dashboard while you migrate to the new Deriv API. -> We’re retiring the Legacy API and moving users to the new Deriv API. Update your apps to keep supporting your clients.
• Explore new API -> Go to new Deriv API
• Go to legacy API -> 'Read the update' which redirects to /updates page
• The rest of the Home page sections below the Hero section are removed

3. Content update on /updates page:

• The new Deriv APIs are here. Is your app ready? -> Important update about the Legacy API

• Your users are moving to the new Deriv APIs. Now's the time to move with them. Update your app to work with the new Deriv APIs. -> We’re retiring the Legacy API and moving users to the new Deriv API. Update your integration now.

• Go to new Deriv APIs -> Go to new Deriv API

• Important: Update your app with the new Deriv APIs -> Important: Update your app with the new Deriv API

• What's happening: Your users are being moved to the new Deriv APIs. Once they move, your app needs to be on the new platform to keep serving them. -> What’s happening: We’re retiring the Legacy API and moving users to the new Deriv API. To keep serving your clients, your app needs to work on the new API.

• What you need to do: Update your app to work with the new Deriv APIs. The new APIs are not compatible with the legacy APIs, so your app will need to be adapted to the new system. -> What you need to do: Update your app to work with the new Deriv API. The new API isn’t compatible with the Legacy API, so you’ll need to adapt your integration.

• Getting started: Create a new account on developers.deriv.com. You'll need to sign up with a different email address. If you want to use your current one, change the email on your legacy account first, then sign up with your preferred email. -> Getting started: Create a new account at developers.deriv.com with an email address that isn't linked to a Legacy API account. If you want to use your current one, change the email on your Legacy API account first, then sign up on developers.deriv.com with your preferred email.

4. Updated the yellow legacy banner content: The Deriv legacy API is being retired. instead of You're on the Legacy Deriv API. We've launched a new and improved version.

5. Moved the yellow legacy banner to appear above the Header (instead of under it).

6. Replaced the CTA button on the yellow legacy banner from "What's New" to "Read the update".

7. Updated Get started section:

• replace 'Sign up with a different email. If you want to use the same email, update it on your legacy account first.' with ''Sign up with a different email. If you want to use your Legacy API email, change it on your Legacy account first.''

8. Generated new translation strings with docusaurus, and applied FR translations provided by translations team.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
deriv-api-docs	Ready	Preview	May 5, 2026 1:10pm