Skip to main content
POST
What each setting does is explained in Routing strategies.

Parameters

Passed in the request body.
string
The email of the member of your organization recorded as the version’s author. Defaults to the person who created the API key, or to the project’s creator for a key without one. The response’s recorded_for_email says which email was recorded.
object
required
The strategy. Each deployment in it is {"model", "provider", "region"}, named as a gateway request names it, the region being a macro region (EU, US, GLOBAL) or the provider’s own (eu-west-1 on Bedrock): the AI gateway’s GET /v1/models lists them. Get benchmark with suggested_routing_strategies gives one made from a finished benchmark.
integer
Omit it to create a strategy. To save the next version, pass the version you read as live: the save is refused with a 409 stale_version when another version has gone live since.
The response also carries blockers (what prevents the usual next step), in plain words. It is empty when the usual workflow applies.