Trigv API

The Trigv API lets your stack send native push alerts to subscribed devices. For most integrators, that means one thing: ingest - POST a JSON event with a workspace API key and Trigv delivers the push. The same platform also exposes mobile and dashboard session routes (Sanctum tokens) for the iOS app and app.trigv.com; this page focuses on ingest and the endpoints you wire from scripts, CI, and automation tools.

Base URL

All API requests use HTTPS. Production base path:

Code

https://api.trigv.com/api

Example ingest URL: https://api.trigv.com/api/v1/events. Always send Accept: application/json so errors return JSON, not HTML redirects.

Authentication

Ingest routes authenticate with a workspace API key in the Authorization header: Bearer trgv_.... Keys are created in the dashboard, shown once at create/rotate, and stored hashed server-side. Never put keys in the JSON body.

See API keys for create, rotate, and revoke. Session routes (app login, device registration) use Sanctum tokens - not workspace keys. See API security for the full credential model.

Primary endpoint - send an event

POST/api/v1/events

Queue a push notification for a channel in your workspace. Required fields: channel (slug) and title. Optional: description, level, delivery_urgency, image_url, url, idempotency_key.

Code

curl -X POST https://api.trigv.com/api/v1/events \
	-H "Content-Type: application/json" \
	-H "Accept: application/json" \
	-H "Authorization: Bearer trgv_YOUR_KEY" \
	-d '{"channel":"general","title":"Deploy finished","level":"success"}'

Full parameter reference: POST /api/v1/events.

Connection test - verify API key

GET/api/v1/connection

Confirms your workspace API key is valid and authorized for ingest. Use this in Zapier, Make, n8n, or OttoKit connection tests. Does not create an event, bill usage, or send a push.

Code

curl -sS "https://api.trigv.com/api/v1/connection" \
	-H "Accept: application/json" \
	-H "Authorization: Bearer trgv_YOUR_KEY"

Success returns 200 OK with workspace and key metadata. Same auth failures as ingest: 401 (invalid key), 403 (revoked/expired/wrong scope), 429 (connection abuse throttle - separate from POST rate limits).

OpenAPI

Machine-readable spec: api.trigv.com/openapi.yaml. Use it for codegen, Postman import, or agent-assisted integration.

Response codes

Common ingest status codes. Full detail: Errors & rate limits.

Code	When
`200`	Duplicate `idempotency_key` - returns existing event, no extra usage
`202`	Event accepted and queued for delivery
`400`	Malformed JSON or invalid request shape
`401`	Missing or invalid Bearer API key
`403`	Revoked/expired key, missing `events:write`, or inactive workspace
`404`	Channel slug not found or inactive
`422`	Validation failed (e.g. missing `channel` or `title`)
`429`	Monthly event cap or per-key burst rate limit (60 req/min default)
`5xx`	Server error - retry with backoff

Rate limits

Each API key defaults to 60 requests per minute (burst). Workspaces also have a monthly event allowance by plan. Both return 429 with different message strings - see Errors & rate limits to tell them apart.

Reference

POST /api/v1/events Ingest Errors & rate limits Reference API security Auth & logging OpenAPI spec YAML