MetriBeacon
Menu

HEAD Measure a job run using its heartbeat URL

/hb/{token}/fail

Empty-body GET, HEAD or POST. /start begins a run; the base URL succeeds; /fail fails; /abort aborts. Only success confirms a scheduled heartbeat. Optional UUID run_id pairs parallel runs and makes repeated identical phases idempotent; conflicting endings return 409. Without an ID only one measurement may be open. A base heartbeat without an open measurement keeps its original behavior. Duration measures server receipt times; missing starts produce no duration. Each new phase consumes one ordinary event; retries do not double charge. Never put secrets in logs or automatically retry uncertain calls without a run ID.

On this page

Access and permissions

Empty-body GET, HEAD or POST. /start begins a run; the base URL succeeds; /fail fails; /abort aborts. Only success confirms a scheduled heartbeat. Optional UUID run_id pairs parallel runs and makes repeated identical phases idempotent; conflicting endings return 409. Without an ID only one measurement may be open. A base heartbeat without an open measurement keeps its original behavior. Duration measures server receipt times; missing starts produce no duration. Each new phase consumes one ordinary event; retries do not double charge. Never put secrets in logs or automatically retry uncertain calls without a run ID.

No account sign-in is required. Any listed browser-origin checks and rate limits still apply.

Parameters and headers

FieldLocationType and limitsRequiredMeaning
tokenPathstring; {"pattern":"^mbh_[A-Za-z0-9_-]{43}$"}YesSecret token copied from this heartbeat monitor.
run_idURL querystring; {"format":"uuid"}NoOptional stable UUID shared by start and completion.

Request body

No request body.

Responses

Stable error codes
unauthorized
Stable error codes
browser_required
csrf
invalid_origin
workspace_scope
access_denied
forbidden
Stable error codes
not_found
Stable error codes
run_conflict
Stable error codes
body_not_allowed
Stable error codes
invalid_request
invalid_run
Stable error codes
quota_exceeded
Stable error codes
unavailable
feature_unavailable

Retries and asynchronous work

This change does not have a general retry guarantee. If the response is unclear, read the affected resource before trying again. Follow Retry-After waiting times and request new sign-in or action codes when they expire.

Request examples

Replace demo IDs, timestamps and placeholders with your own values. For a retry, keep the same IDs, time and content. These examples do not run requests on this page.

Keep login links, codes, cookies and keys private. Do not print them in logs or share them in support requests.

shell
curl --fail --silent --show-error --request HEAD "https://metribeacon.com/hb/YOUR_HEARTBEAT_TOKEN/fail"
python
import urllib.request
request = urllib.request.Request('https://metribeacon.com/hb/YOUR_HEARTBEAT_TOKEN/fail', method='HEAD', headers={})
with urllib.request.urlopen(request) as response:
    print(response.status)
javascript
const response = await fetch("https://metribeacon.com/hb/YOUR_HEARTBEAT_TOKEN/fail", {method:"HEAD", credentials:"same-origin", headers:{}});
console.log(response.status);
go
package main
import("fmt";"net/http")
func main(){ request,_:=http.NewRequest("HEAD","https://metribeacon.com/hb/YOUR_HEARTBEAT_TOKEN/fail",nil);
response,err:=http.DefaultClient.Do(request);if err!=nil{panic(err)};defer response.Body.Close();fmt.Println(response.StatusCode) }
  • HTTP API, OAuth and MCP

    Find the user API endpoints, their permissions, fields, examples and response formats.

  • GET Measure a job run using its heartbeat URL

    Empty-body GET, HEAD or POST. /start begins a run; the base URL succeeds; /fail fails; /abort aborts. Only success confirms a scheduled heartbeat. Optional UUID run_id pairs parallel runs and makes repeated identical phases idempotent; conflicting endings return 409. Without an ID only one measurement may be open. A base heartbeat without an open measurement keeps its original behavior. Duration measures server receipt times; missing starts produce no duration. Each new phase consumes one ordinary event; retries do not double charge. Never put secrets in logs or automatically retry uncertain calls without a run ID.

  • POST Measure a job run using its heartbeat URL

    Empty-body GET, HEAD or POST. /start begins a run; the base URL succeeds; /fail fails; /abort aborts. Only success confirms a scheduled heartbeat. Optional UUID run_id pairs parallel runs and makes repeated identical phases idempotent; conflicting endings return 409. Without an ID only one measurement may be open. A base heartbeat without an open measurement keeps its original behavior. Duration measures server receipt times; missing starts produce no duration. Each new phase consumes one ordinary event; retries do not double charge. Never put secrets in logs or automatically retry uncertain calls without a run ID.

  • GET Measure a job run using its heartbeat URL

    Empty-body GET, HEAD or POST. /start begins a run; the base URL succeeds; /fail fails; /abort aborts. Only success confirms a scheduled heartbeat. Optional UUID run_id pairs parallel runs and makes repeated identical phases idempotent; conflicting endings return 409. Without an ID only one measurement may be open. A base heartbeat without an open measurement keeps its original behavior. Duration measures server receipt times; missing starts produce no duration. Each new phase consumes one ordinary event; retries do not double charge. Never put secrets in logs or automatically retry uncertain calls without a run ID.