StatusCake

Adding tests through the StatusCake API with Postman

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:

POSTMANB

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.

POSTMANC

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.

POSTMAND

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.

POSTMANE

Share this

More from StatusCake

What the Namecheap Outage Revealed About DNS Recovery

4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes

Monzo’s Stand-In Held Up on Wednesday. Some Customers Still Had a Bad Day.

3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and

What Broke GitHub on August 17 and How Retries Made the Incident Worse

3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests

Automate StatusCake Monitoring with viaSocket

3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect

Website Monitoring Checklist: What to Track Beyond Uptime

7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and

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

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.