version_unavailable: This route is newer than the pinned version
The route was added in a later API version than the one the request is pinned to (by Dynamo-Version or the account default). It answers as if it did not exist, so a client written against the older version never sees a shape it does not know.
Only the multi-tenant hosted front door answers this code, on the owner, payee and oracle routes. A request that names no Dynamo-Version is served the account's default version, which is 1.8.0 for new accounts. A single-tenant core serves every route it has, whatever version the request names.
What to do
- Send a newer
Dynamo-Versionon this request; the message names the version the route needs. - Or move the account default with
PUT /tenant/v1/settings {defaultVersion}.
On the wire
HTTP 404, error type not_found.
{
"error": "version_unavailable",
"errorDetail": {
"type": "not_found",
"code": "version_unavailable",
"message": "this route needs Dynamo-Version 1.6.0 or later (served 1.5.0)",
"param": null,
"doc_url": "…/errors/version_unavailable.md",
"fix": "this route was added after the version you pinned; send a newer Dynamo-Version or change the tenant default"
}
}
See all error codes.