Today, we added a first draft of the BookBeat Status API, which is a very simple way for us to push information about server and backend problems to our clients. We will evaluate if this is a sufficient solution for this critical function and replace it with something more sophisticated if needed, e.g. if GitHub’s website response times are too slow.

The current version has support for localization and multiple environments, like prod, test and dev. The FATAL status should always have a translation fallback in each client, so that the support doesn’t have to specify an status message if a critical error must be published asap, but all other should be translated here and not displayed in the client if a message isn’t specified.

Explore the API from the discovery root url.