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
Recently we’ve had a lot of requests for examples of how add new tests through the StatusCake API using the popular Postman tool. In this article we’ll take you through some of the steps required to get you going with this method, below you’ll find an example for each test type we offer, taking you through the process of adding a test.
Authentication
First off we need to cover the authentication method that will be required to make the API calls through Postman, you will need to obtain your API key and username from the “User Details” section of the StatusCake App, these should then be input into the “Headers” Section of Postman as shown below:
Uptime Testing
Now that all of our calls will carry with them the required authentication details, we can look at how to proceed in setting up the tests.
Taking the fields from our API documentation you should enter the settings that you’d like applied to the Uptime test that you are adding, every time an uptime test is created you must at least include as a minimum: TestType, Checkrate, WebsiteName, and WebsiteURL. The call should be submitted as PUT.
Page Speed Testing
Page speed testing works similarly, and you can grab the fields that can be used from our API docs here. The required fields for this one are: name, website_url, location_iso, and checkrate. The POST method is required for this one.
SSL Testing
For SSL testing the PUT method should be utilized, and the required fields are: domain, checkrate, contact_groups, alert_at, alert_expiry, alert_reminder, alert_broken and alert mixed.
StatusCake Team
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