Migrate to Arrow 2
Replace retiring Arrow 1 model IDs before October 16, 2026.
Arrow 1 and Arrow 1.1 retire on October 16, 2026. Update requests using any of these model IDs before then:
arrow-previewarrow-1arrow-1.1arrow-1.1-max
After retirement, requests using these IDs return 404 model_not_found. They do not automatically switch to Arrow 2.
Change the model field from one of the IDs above to arrow-2. For example, change "model": "arrow-1.1" to "model": "arrow-2". Arrow 2 Telos (arrow-2-telos) is another option if it is available to your organization. Check GET /v1/models for available models and supported operations.
We recommend creating a new project API key for Arrow 2 in the API Platform, with the permissions your integration needs. See API keys for key scope and replacement guidance.
Read the Arrow 2 model guide for availability and token pricing. Check Text to SVG parameters for generation input limits.
See the API Reference for request and response formats. If you use the Responses API, see Migrate to Responses for its separate contract.