routing

List Automatic Fallbacks

Changed on

The models the caller's organization sent requests to in the last 30 days, and the fallback each gets.

A request that sends a model's catalog ID moves to the model's next offering when one fails, with no policy. Each model lists its offerings in the order such a request tries them, priced for this organization, with who runs the built-in tools on each, beside its traffic: how many requests a backup served, and how many named one offering and so had no fallback. The traffic is the workspaces the caller may see in their active organization, by the rule the organization's usage reads use.

get/api/v1/organizations/me/automatic-fallbacks

Request

  • The document declares no server URL.
  • Auth: one of:
    • API key in header Otari-Key
    • API key in header x-api-key

Response

Successful Response

window_daysinteger required

How many days of traffic the counts cover.

Changes