Legacy Data API endpoints retired November 4, 2026
Replace /api/v2/data/* requests, which now return 410 Gone, with supported V2 endpoints. Your existing API key still works.
Find the supported endpoint
Each legacy endpoint has a Free and Pro replacement. Free endpoints return fewer fields.
| Data | Legacy path | Free replacement | Pro replacementAbout Pro |
|---|---|---|---|
| Language models | /api/v2/data/llms/models | /api/v2/language/models/free | /api/v2/language/models |
| Text to image | /api/v2/data/media/text-to-image | /api/v2/media/text-to-image/models/free | /api/v2/media/text-to-image/models |
| Image editing | /api/v2/data/media/image-editing | /api/v2/media/image-editing/models/free | /api/v2/media/image-editing/models |
| Text to video | /api/v2/data/media/text-to-video | /api/v2/media/text-to-video/models/free | /api/v2/media/text-to-video/models |
| Image to video | /api/v2/data/media/image-to-video | /api/v2/media/image-to-video/models/free | /api/v2/media/image-to-video/models |
| Text to speech | /api/v2/data/media/text-to-speech | /api/v2/media/text-to-speech/models/free | /api/v2/media/text-to-speech/models |
Update your integration
- 01
Review the replacement endpoint
Use the table above to find the supported endpoint. Read the API documentation for its access requirements and response schema.
- 02
Update your implementation
Replace the legacy path. Update request parameters and response handling to match the documentation. Keep your existing API key.
- 03
Test and deploy
Test the updated integration, then deploy it. Legacy requests return
410 Gonewith a link to this guide.
Need help migrating?
Contact us if a replacement omits a field you use or you need higher request limits. We can also help with redistribution rights. Include the legacy endpoint and fields your integration uses.