To better support developer needs and enhance security, we’re implementing API authentication for VisionAgent. These changes will prevent unauthorized access and API misuse while ensuring reliable service for users.As part of the API authentication implementation, we’re changing the endpoint that VisionAgent calls.These changes will go into effect on April 11, 2025.To ensure that VisionAgent and VisionAgent-generated code continue to work correctly, please follow the instructions in the sections below before April 11, 2025.
Action Required: If You Directly Call the VisionAgent Endpoint
If you created code that directly calls the VisionAgent endpoint, you must change the endpoint before April 11, 2025, in order for the code to work.Change the endpoint from:api.landing.aito:api.va.landing.aiIf you get errors caused by an HTTP 301 redirect, update the endpoint to resolve the issue.
The VisionAgent web app is available here. When you deploy generated code in the VisionAgent web app, the deployed code calls the VisionAgent endpoint.Any code deployed before April 11, 2025 will need to be re-deployed in order for it to call the correct endpoint.Any code deployed after April 11, 2025 will call the correct endpoint.