# The key check in front of /api/public says whether to send the call again

- Date: 2026-10-29
- Type: Non-breaking change
- Surface: /api/public
- What you need to do: Nothing.
- Address: https://developers.rivr.io/changelog/2026-10-29-key-check-retry-signal

The errors the organisation-key check in front of /api/public answers itself (`key_invalid`, `organization_required`, `organization_invalid`, `organization_not_accessible`, `route_not_available` and `access_check_unavailable`) now carry `retryWhen` as the last member of the body and the header `Rivr-Should-Retry`. The values are the ones the code's page gives; only `access_check_unavailable` is `same_request`, so it is the only one with `Rivr-Should-Retry: true`. Nothing else changes, and the answers /api/public itself gives are untouched. public-api 0.28.0, in the sandbox and in production the same day.