Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
The StatusCake API allows users of the platform to come up with custom ways of interacting and making our tools work for their specific needs. In this blog post I’m going to look at a few recent projects on GitHub that use the StatusCake API to either save you time or do something interesting with your test data.
status-cake-push-client
vparpoil/status-cake-push-client: Python App to push regular updates to StatusCake (github.com)
In some instances, it’s not possible for StatusCake uptime tests to monitor certain secure system configurations. We offer a workaround for this, push monitoring. Push monitoring is the reverse of a standard uptime test, your server or device contacts our service to let us know it is still active. This is sometimes known as heartbeat monitoring.
This application created by GitHub user vparpoil is a allows a user to easily create the following type of PUSH tests:
- Ping tests
- MongoDB Connection tests
- Curl test with string match
- Port testing
Requirements
- Python
- (Optional) The pymongo python package
You can get a unique push test URL by navigating to the Push Test tab found under the uptime monitoring section to the left of the StatusCake status page.
Once you have set up your test you’ll receive a unique URL that will look something like this:
Next, all you need to do is create a tests.json file, and add a test including the required test details and your unique URL in the StatusCakeUrl property, like this basic ping test:
Tip: you can just copy the existing testsSample.json and remove/duplicate tests you need or don’t need.
StatusCake Exporter
chelnak/status-cake-exporter: A Prometheus exporter for StatusCake (github.com)
This application created by GitHub user chelnak is a Prometheus exporter for StatusCake test data. Prometheus is a tool that’s used for monitoring applications and services, it allows users to store time series metrics. In this project it is used with Grafana to render the metrics into charts, graphs and other flexible visualizations.
Requirements:
- Docker
- Python 3.7 with the following dependencies:
- prometheus-client==0.7.1
- requests==2.22.0
- ConfigArgParse==0.14.0
- setuptools==58.3.0
- Kubernetes (optional)
- Helm 3 (optional)
Once you’ve cloned the repo and followed the configuration steps listed in the readme you’ll be able to export the results of your StatusCake uptime tests to Grafana and produce something like this statusmap panel to get a useful visualisation.
This sort of visualisation is bound to win you some brownie points with management!
statuscake-go
StatusCakeDev/statuscake-go: StatusCake Go SDK (github.com)
The Go implementation of the StatusCake API client. This is one of ours!
Requirements:
- one of the last three major releases of Go
You’ll need to either use Go module support to import the dependencies or just install the StatusCake-go package using the command:
Once installed, open or create a .go file, instantiate an API client and execute a request, like so:
Couldn’t get any simpler than that! You should also keep an eye on our implementations for JavaScript and Python, they are both sill in alpha right now but that shouldn’t stop you from talking a look, we’d love your feedback.
You can view these and our other repositories here.
X-RM Blink1 Service
x-rm/Blink1-StatusCake (github.com)
This application controls a small Blink(1) device. Blink(1) started as a Kickstarter project and allows a user to configure the colour, brightness and pattern of a small USB LED dongle. Users of a Blink(1) device will usually configure this with a service such as IFTTT but GitHub user nmg196 has created a configurable application that checks the status of a user’s StatusCake uptime tests & SSL and will cause the Blink(1) device to emit a bright red warning light if there are any failed tests.
If you own a Blink(1) all you need to do to get set up is clone the repo and update the App.config file with your StatusCake username and API key in before installing the Windows Service. Pretty niche, but this project stood out as being quite a novel use of the StatusCake API!
Conclusion
I’ve touched on a few projects found on GitHub that can enrich your StatusCake experience, but don’t stop here, there are many more out there to be found. Have look yourself, perhaps you’ll find a project that will be a perfect solution for you, or perhaps you’ll get inspired to create your own. Cheers!
Christopher Long
Share this
More from StatusCake
Engineering
Beyond Uptime: Building a Self-Healing OpenClaw Observability Stack
3 min read The allure of OpenClaw is undeniable. You deploy a highly autonomous, self-hosted AI agent, give it access to your repositories and inboxes, and watch it reason through complex workflows while you sleep. It is the dream of the ultimate 10x developer tool realized. But as any veteran DevOps engineer will tell you: running an LLM-backed
Daniel
April 23, 2026
When AWS us-east-1 Fails, Much of the Internet Fails With It
7 min read There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure,
James Barnes
April 15, 2026
In the Age of AI, Operational Memory Matters Most During Incidents
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
James Barnes
April 10, 2026
AI Didn’t Kill the SDLC. It Made It Harder to See
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
James Barnes
April 2, 2026
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026