Skip to content

Redwood City

  • Quiet failures247+19%
  • Median notice41 sec−38%
Live monitors347
VectornosisDocsOpen workspace
On this page
  1. Authenticate
  2. Prefer idempotent workers
  3. Handle errors
  4. Related

API

API overview

Current surface focuses on webhooks, freshness workers, and alert tests. A broader customer REST catalog ships with paid live monitoring.

Steps

  1. Authenticate

    Use workspace secrets / API keys as configured in your environment — never commit them.

  2. Prefer idempotent workers

    Freshness checks should be safe to run on a schedule.

  3. Handle errors

    Non-2xx responses should page your deploy pipeline, not silent-fail overnight.