Resources / EventAPI Documentation

EventAPI reference

Point your alerts, monitors, and automations at a single webhook and we'll turn them into incidents your SREs can act on — with severities, labels, and optional runbooks.

High/critical auto-pages on-callPrometheus · Grafana · Datadog · Uptime KumaOne payload format, many tools

Where to manage keys

API keys are created and rotated inside your Tech Guys 2 Go portal. Each key is used as a Bearer token for this webhook.

Go to Portal → Settings → API keys
Copy the one-time secret value
Paste it as your Authorization header

Endpoint & authentication

The ingest webhook is a simple JSON-over-HTTPS endpoint. Most customers start by sending alerts from existing tools, then layer on more context (entities, runbooks, and AI hints) over time.

HTTP details

POST to:

https://ingest.techguys2go.com/api/webhook/ingest

Required header:

Authorization: Bearer <YOUR_API_KEY>

Requests without a valid bearer token will be rejected with 401 Unauthorized.

Base JSON payload

{
  "summary": "K8s prod API 5xx spike",
  "severity": "high",          // low | medium | high | critical
  "labels": {
    "service": "api",
    "env": "prod",
    "host": "app01.prod.example.com"
  },
  "details": "5xx spiking since 12:03 UTC, ingress timeouts",
  "entityId": "YOUR_ENTITY_ID_OPTIONAL",
  "runbookId": "YOUR_RUNBOOK_ID_OPTIONAL"
}

Field reference

Field	Type	Required	Description
summary	string	Yes	One-line description of what's happening. This is what shows up first in incident lists and pages.
severity	enum (low, medium, high, critical)	Yes	Drives paging behavior and prioritization. high and critical typically trigger on-call.
labels	object	Recommended	Free-form key/value pairs (service, env, region, host, team, etc.). Used for routing, grouping, and dashboards.
details	string	Optional	Longer description, stack traces, or useful context. Shown in the incident body.
entityId	string	Optional	If you use our entity model, you can link this alert to a specific service/host/system.
runbookId	string	Optional	Points the incident at a recommended runbook so responders know exactly where to start.

Any extra fields you send will be preserved and surfaced in the incident details for your team.

Vendor-specific examples

Start with cURL to test your endpoint, then use the matching snippet for your alerting tool. All of them send into the same webhook and payload shape.

Replace YOUR_DOMAIN and YOUR_API_KEY with values from your portal.

curl -X POST https://ingest.techguys2go.com/api/webhook/ingest \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
  "summary": "K8s prod API 5xx spike",
  "severity": "high",
  "labels": {
    "service": "api",
    "env": "prod",
    "host": "app01.prod.example.com"
  },
  "details": "5xx spiking since 12:03 UTC, ingress timeouts",
  "entityId": "YOUR_ENTITY_ID_OPTIONAL",
  "runbookId": "YOUR_RUNBOOK_ID_OPTIONAL"
}'

These examples are intentionally minimal. In real environments, you'll often include more labels (team, region, feature flag, etc.) and richer details.

Want help wiring this into your stack?

We can pair with your team to connect existing monitors, define a simple severity model, and attach runbooks so pages feel calm, not chaotic.