1Get access token 120 ms
POST /v1/api/token
password stored encrypted
{{access_token}}
2Check API 514 ms
POST /v1/api/orders/status
200$.result.status = SUCCESS
UpTotal 634 ms

Multi-step API monitoring.
Log in, pass the token,
check the API.

Monitor APIs that require authentication or several dependent requests - as one monitor with one status. Each check gets a token, uses it in the next request and verifies the answer, around the clock.

Get startedSee plans

What multi-step monitoring is for.

APIs behind a login

Most real APIs answer only with a token. One monitor logs in with your credentials, takes the token from the answer and calls the API with it - on every check, with nobody renewing anything by hand.

Requests that depend on each other

Create something and read it back, look up an id and use it in the next call, walk through a checkout: any value from one step's JSON answer can be used in the URL, headers or body of the steps after it.

One monitor, one status, one incident

All steps belong to a single monitor: one status, one incident timeline, one set of alerts. If a step fails, the following steps are skipped and the incident says which step it was.

From every check location

The whole flow runs from each location you pick, public or private, and every location keeps its own result. Tokens are never shared between locations.

Every step timed

The monitor page shows each step's result and response time and the total, so you see whether the login or the API itself got slower.

Test before you save

Run one step or the whole flow from the form and see every step's result right away. Nothing is stored and no alert is sent.

Enter credentials once, safely.

Put passwords, test ids and anything you reuse into variables and write them in your steps as {{NAME}}. Mark the sensitive ones as secret: they are stored encrypted and never shown again.
Variables
AUTH_PASSWORD•••••••••••• Secret
CUSTOMER_ID•••••••• Secret
REGIONtehran Secret
{
  "UserName": "monitor",
  "Password": "{{AUTH_PASSWORD}}"
}
Step 1 response
{
  "result": { "content": "eyJhbGciOi…" }
}
$.result.content→{{access_token}}
Step 2 header
Authorization: Bearer {{access_token}}

Take a value from one answer, use it in the next request.

Point at a field of the JSON answer, give it a name, and use it in the next steps' URL, headers or body. If the value is missing or empty the step fails - an empty token never reaches your API.

Know which step broke, and why.

Login failures, timeouts, unexpected status codes and failed JSON checks are told apart, per step. The incident and the alert carry the same sentence, so nobody has to guess.
Failed step
Step 1 - Get access token
Invalid credentials
Step 1 Get access tokenFailed88 ms
Step 2 Check APISkipped-
Latest runs
New token, valid for 60 minutes 10:00
Token still valid - login skipped 10:05
Token still valid - login skipped 10:10
About to expire - new token first 10:59

Tokens renewed before they expire.

Keep a token between checks until it expires instead of logging in every time. A new one is fetched shortly before the old one runs out - and at once if your API refuses it.

Careful with your credentials.

Secrets stored encrypted

Passwords and other values you mark as secret are encrypted before they are stored, and are never sent back to the browser - not even to your own teammates.

Hidden in logs, incidents and alerts

Secret values and tokens are masked wherever a result is shown: test results, incidents, alerts. The answer of a login step is not stored at all.

No code, no surprises

Variables are plain text placeholders - nothing is executed. Redirects are not followed, so a token is never sent to another address.

All you really care about
monitored in one place.

From websites and APIs to servers and cron jobs, noc724 watches every layer. Eight monitor types, one dashboard.

Website monitoring

Keyword monitoring

Ping monitoring

Port monitoring

Cron job monitoring

DNS monitoring

API monitoring

UDP monitoring

SSL monitoring

Frequently asked questions.

A monitor that sends several HTTP requests in order as one check. Each step can check its status code and JSON answer and hand values - like an access token - to the steps after it. The monitor is up only when every step passes.

8

monitor types

15s

fastest checks

Monitor the whole flow, not just one request.

Included in the paid plans.

Get started