Alerts, webhooks and integrations
Alerts, webhooks and integrations for your data calls
See it working
Open alerts
Alerts that are firing now. Acknowledge one to say you're on it (PagerDuty and Opsgenie are told too); it resolves on its own once the metric recovers.
CriticalError rate 31% on Example Eta
31 of 100 calls failed in 5 minutes (threshold 25%). Most were 401: check the vendor key.
Started Sep 30, 09:00 UTC · seen 4 times
Timeline (3)
- Sep 30, 09:00 UTC Error rate 31% (threshold 25%).
- Sep 30, 09:00 UTC Sent to #gtm-oncall.
- Sep 30, 09:00 UTC Paged PagerDuty: data platform.
Alert rules
Each rule watches one metric in a window and opens an alert when it crosses the threshold. Repeats are grouped into the open alert; after it resolves, the rule stays quiet for its cooldown.
Error rate above 25%CriticalFiringDefault
Alerts when 25% or more of calls for example-eta fail over 5 minutes (once there are at least 20 calls).
Failed share of calls per provider, over 5 minutes.
Checked on every call · Notifies #gtm-oncall, PagerDuty: data platform, On-call email · dashboard toast · last 31% at Sep 30, 15:59 UTC
Spend over $5 in 5 minutesWarningOKDefault
Alerts when calls cost $5.00 or more within 5 minutes.
Checked on every call · Notifies #gtm-oncall, PagerDuty: data platform, On-call email · dashboard toast · last $1.24 at Sep 30, 15:59 UTC
Billing mismatch on any providerWarningOK
Alerts when 1 or more calls are billed against the vendor's published rule within an hour.
A provider charged for a call its published rule says is free.
Checked every 5 minutes · Notifies #gtm-oncall, PagerDuty: data platform, On-call email · dashboard toast · last 0 at Sep 30, 15:59 UTC
Key used from a new IPInfoOKDefault
Alerts when a key is used from an IP address it hasn't used before.
Raised when it happens · Notifies On-call email · dashboard toast
History
Resolved alerts, newest first, with who was notified and when. Kept for the last 2,000 alerts.
No resolved alerts yet.
What you get
Alert rules on every metric that matters
Error rate, p95 latency, spend, budget used, provider failure spikes, failing vendor keys, billing mismatches, cache hit rate, delivery backlog and security events, scoped to the workspace, a key, a provider or a capability.
Native destinations
Email (immediate or digest), Slack, Discord, Microsoft Teams, PagerDuty and Opsgenie, each with its own minimum severity and resolve notifications.
Signed webhooks
Standard Webhooks signatures, retries with backoff, delivery history, replay and test events for alerts and job events.
Alerts with a lifecycle
Alerts open, group repeats, get acknowledged (PagerDuty and Opsgenie are told), resolve on their own when the metric recovers, and respect a cooldown.
Log drains
Stream calls, runs, jobs and alerts to a webhook, Datadog, Axiom, S3, GCS or R2, batched and retried.
How it works
Connect a destination: Slack, PagerDuty, Opsgenie, Teams, Discord, email or a webhook.
Start from the default rules or add your own threshold, window and scope.
Acknowledge from the dashboard or your incident tool; alerts resolve when the metric recovers.
curl https://api.gridrouter.io/v1/alerts/rules \
-H "Authorization: Bearer $GRID_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Email finding failing",
"metric": "vendor_failure_spike",
"threshold": 0.33,
"window_s": 600,
"min_events": 25,
"severity": "critical",
"scope": { "type": "capability", "value": "people.email.find" }
}'Questions
Can I get alerts in Slack or PagerDuty?
Yes. Slack, Discord, Microsoft Teams, PagerDuty and Opsgenie are native destinations, alongside email and signed webhooks. Acknowledging in GridRouter also acknowledges in PagerDuty and Opsgenie.
How fast do alerts fire?
Error rate, spend, provider failures, vendor key failures and billing mismatches with windows up to an hour run on the live stream and fire within seconds. Latency, cache hit rate, budgets and longer windows are evaluated every five minutes.
Will one bad minute page us?
Rate rules wait for a minimum number of calls in the window, repeats group into the open alert, and a cooldown keeps a resolved alert quiet. You can also mute a rule for a while.
Which drains are supported?
Any HTTPS webhook, Datadog, Axiom, Amazon S3 (or S3-compatible), Google Cloud Storage and Cloudflare R2.
More in GridRouter
- Unified API and routingAsk for a capability, not a provider. GridRouter picks the provider, falls back on a miss or an error, and answers in one schema.
- MCP serverPoint any MCP client at one URL and your agent can search the catalog, get a quote and call any capability, inside the budget you set.
- WaterfallsPut providers in order, choose how fast and how far to go, and publish the result as a versioned endpoint your code and agents can call.
- Logs and log explorerSee exactly what every provider returned, what it cost and how long it took, from the dashboard, the API, the CLI or your agent.
- Vendor billing verificationGridRouter checks what each provider charged against what its own pricing says, call by call, and hands you the mismatches as a CSV.
- Private cacheStop paying twice for the same person or company. Every answer is cached for your workspace only and reused until its fields expire.
- Security and governanceYour vendor keys, data and spend stay inside your workspace, and every change is on the record.
- Provider catalog and docsFind the right provider for a capability, see how it bills and what its API looks like, before you sign a contract.