Skip to content
Agentic FabriqGet a demo
All integrations

StatusCake

DEVELOPER · DEVELOPER

Uptime, pagespeed, SSL and heartbeat checks with their history in that account.

Connect StatusCake with Fabriq Developer

Your user pastes their StatusCake credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.

from af_sdk import AgenticFabriq

af = AgenticFabriq()                      # reads AF_APP_ID / AF_APP_SECRET

url = await af.initiate_connection(request, provider="statuscake", method="api_key")
return redirect(url)                      # an AF-hosted page, not yours

async with await af.for_user(request) as session:
    tools = await session.get_tools()     # only what this user granted

Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.

Connecting StatusCake in practice

StatusCake ties its API rate limit to your subscription: an account without one is capped at 60 requests per minute, a paid account has no per-minute cap, and both share a burst limit of 5 requests per second. The quota is per account "regardless of which token was used", so issuing a second token buys no extra throughput.

Scopes that draw scrutiny

  • Authorization: Bearer ${API_TOKEN} One account-wide bearer token with no scopes, and multiple tokens share a single quota, so there is no way to isolate an agent’s traffic from the rest of the account.

Rate limits

  • Accounts without a subscription: a maximum of 60 requests per minute.
  • Accounts with a paid subscription: no per-minute limit.
  • All accounts: a burst limit of 5 requests per second.
  • Headers are x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset, where the limit header carries a composite such as "5, 60;w=60, 5;w=1" and the first value is the limit currently enforced.
  • Over the limit returns 429, and x-ratelimit-reset gives the seconds until the enforced limit lifts.

Worth knowing

  • The composite x-ratelimit-limit value means a naive parser reads "5" as the whole story and misses the per-minute window entirely.
  • Pagination defaults to 25 and caps at 100, so a large estate of checks is always several pages.
  • Several fields are enums rather than free integers: an SSL check rate must be one of 300, 600, 1800, 3600, 86400 or 2073600 seconds.
  • SSL alert scheduling requires "exactly 3 numerical values" for the days on which alerts fire, so you cannot supply one or five.

Checked against StatusCake API reference (2026-09-29), API rate limiting (2026-09-29)

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

statuscake_delete_contact_groups_by_group_idWRITE

Delete a contact group via DELETE /contact-groups/{group_id}. Deletes a contact group with the given id.

api
statuscake_delete_heartbeat_by_test_idWRITE

Delete a heartbeat check via DELETE /heartbeat/{test_id}. Deletes a heartbeat check with the given id.

api
statuscake_delete_maintenance_windows_by_window_idWRITE

Delete a maintenance window via DELETE /maintenance-windows/{window_id}. Deletes a maintenance window with the given id.

api
statuscake_delete_pagespeed_by_test_idWRITE

Delete a pagespeed check via DELETE /pagespeed/{test_id}. Deletes a pagespeed check with the given id.

api
statuscake_delete_ssl_by_test_idWRITE

Delete an SSL check via DELETE /ssl/{test_id}. Deletes an SSL check with the given id.

api
statuscake_delete_uptime_by_test_idWRITE

Delete an uptime check via DELETE /uptime/{test_id}. Deletes an uptime check with the given id.

api
statuscake_get_contact_groupsREAD

Get all contact groups via GET /contact-groups. Returns a list of contact groups for an account.

api
statuscake_get_contact_groups_by_group_idREAD

Retrieve a contact group via GET /contact-groups/{group_id}. Returns a contact group with the given id.

api
statuscake_get_heartbeatREAD

Get all heartbeat checks via GET /heartbeat. Returns a list of heartbeat checks for an account.

api
statuscake_get_heartbeat_by_test_idREAD

Retrieve a heartbeat check via GET /heartbeat/{test_id}. Returns a heartbeat check with the given id.

api
statuscake_get_maintenance_windowsREAD

Get all maintenance windows via GET /maintenance-windows. Returns a list of maintenance windows for an account.

api
statuscake_get_maintenance_windows_by_window_idREAD

Retrieve a maintenance window via GET /maintenance-windows/{window_id}. Returns a maintenance window with the given id.

api
statuscake_get_pagespeedREAD

Get all pagespeed checks via GET /pagespeed. Returns a list of pagespeed checks for an account.

api
statuscake_get_pagespeed_by_test_idREAD

Retrieve a pagespeed check via GET /pagespeed/{test_id}. Returns a pagespeed check with the given id.

api
statuscake_get_pagespeed_by_test_id_historyREAD

Get all pagespeed check history via GET /pagespeed/{test_id}/history. Returns a list of pagespeed check history results for a given id, detailing the runs performed on the StatusCake testing infrastruture. The returned results are a paginated series. Alongside the response data is a `links` object referencing the current response document, `self`, and the next page in the series, `next`. Aggregated data over the specified duration is returned in the root level `metadata` field.

api
statuscake_get_pagespeed_locationsREAD

Get all pagespeed monitoring locations via GET /pagespeed-locations. Returns a list of locations detailing server information for pagespeed monitoring servers. This information can be used to create further checks using the API.

api
statuscake_get_sslREAD

Get all SSL checks via GET /ssl. Returns a list of SSL checks for an account.

api
statuscake_get_ssl_by_test_idREAD

Retrieve an SSL check via GET /ssl/{test_id}. Returns an SSL check with the given id.

api
statuscake_get_uptimeREAD

Get all uptime checks via GET /uptime. Returns a list of uptime checks for an account.

api
statuscake_get_uptime_by_test_idREAD

Retrieve an uptime check via GET /uptime/{test_id}. Returns an uptime check with the given id.

api
statuscake_get_uptime_by_test_id_alertsREAD

Get all uptime check alerts via GET /uptime/{test_id}/alerts. Returns a list of uptime check alerts for a given id. The returned results are a paginated series. Alongside the response data is a `links` object referencing the current response document, `self`, and the next page in the series, `next`.

api
statuscake_get_uptime_by_test_id_historyREAD

Get all uptime check history via GET /uptime/{test_id}/history. Returns a list of uptime check history results for a given id, detailing the runs performed on the StatusCake testing infrastruture. The returned results are a paginated series. Alongside the response data is a `links` object referencing the current response document, `self`, and the next page in the series, `next`.

api
statuscake_get_uptime_by_test_id_periodsREAD

Get all uptime check periods via GET /uptime/{test_id}/periods. Returns a list of uptime check periods for a given id, detailing the creation time of the period, when it ended and the duration. The returned results are a paginated series. Alongside the response data is a `links` object referencing the current response document, `self`, and the next page in the series, `next`.

api
statuscake_get_uptime_locationsREAD

Get all uptime monitoring locations via GET /uptime-locations. Returns a list of locations detailing server information for uptime monitoring servers. This information can be used to create further checks using the API.

api
statuscake_post_contact_groupsWRITE

Create a contact group via POST /contact-groups. Creates a contact group with the given parameters.

api
statuscake_post_heartbeatWRITE

Create a heartbeat check via POST /heartbeat. Creates a heartbeat check with the given parameters.

api
statuscake_post_maintenance_windowsWRITE

Create a maintenance window via POST /maintenance-windows. Creates a maintenance window with the given parameters.

api
statuscake_post_pagespeedWRITE

Create a pagespeed check via POST /pagespeed. Creates a pagespeed check with the given parameters.

api
statuscake_post_sslWRITE

Create an SSL check via POST /ssl. Creates an SSL check with the given parameters.

api
statuscake_post_uptimeWRITE

Create an uptime check via POST /uptime. Creates an uptime check with the given parameters.

api
statuscake_put_contact_groups_by_group_idWRITE

Update a contact group via PUT /contact-groups/{group_id}. Updates a contact group with the given parameters.

api
statuscake_put_heartbeat_by_test_idWRITE

Update a heartbeat check via PUT /heartbeat/{test_id}. Updates a heartbeat check with the given parameters.

api
statuscake_put_maintenance_windows_by_window_idWRITE

Update a maintenance window via PUT /maintenance-windows/{window_id}. Updates a maintenance window with the given parameters.

api
statuscake_put_pagespeed_by_test_idWRITE

Update a pagespeed check via PUT /pagespeed/{test_id}. Updates a pagespeed check with the given parameters.

api
statuscake_put_ssl_by_test_idWRITE

Update an SSL check via PUT /ssl/{test_id}. Updates an SSL check with the given parameters.

api
statuscake_put_uptime_by_test_idWRITE

Update an uptime check via PUT /uptime/{test_id}. Updates an uptime check with the given parameters.

api

Put StatusCake behind one governed endpoint.

Same permissions, same audit trail, whatever else you connect next.