How Trigv works

Trigv sends alerts from your tools to your phone - Zapier, a cron job, a script, or an AI agent. You trigger an alert; Trigv delivers a native push to subscribed devices. We deliver the message but don’t keep it on our servers - title and body stay on your device in searchable local history.

Base URL

All API requests use HTTPS:

Code

https://api.trigv.com

The public ingest endpoint is POST /api/v1/events (full URL: https://api.trigv.com/api/v1/events).

Authentication

Ingest requests authenticate with a workspace API key sent in the Authorization header as Bearer trgv_.... Keys are created and managed in the dashboard at app.trigv.com. Each new workspace receives a default key at signup; you can create additional named keys per workspace. See API security for key handling best practices.

Field / Header	Value	Description
`Authorization`	`Bearer trgv_XXXXXXXX_…`	Required. Plain-text key shown once at creation; stored hashed server-side.
`Content-Type`	`application/json`	Required for `POST /api/v1/events`.
`Accept`	`application/json`	Recommended - ensures JSON error responses instead of HTML redirects.
`api_key` (body)	-	Rejected. Do not send keys in the JSON body.

Manage keys in the dashboard: create named keys, rotate (old key stops working immediately), and revoke. See API keys guide for details.

OpenAPI spec: api.trigv.com/openapi.yaml

API key format:

Code

trgv_{8 alphanumeric}_{32 alphanumeric}

Invalid API key (401)

Code

{
	"message": "Invalid API key."
}

Revoked or restricted key (403)

Examples: revoked key, expired key, missing events:write scope, or inactive workspace.

Code

{
	"message": "This API key has been revoked."
}

Core concepts

Workspace - owns API keys, channels, events, billing, and monthly usage counters.
Channel - a named routing target (slug, e.g. general). Devices subscribe to channels via the mobile app.
Event - server-side metadata record (status, level, timestamps, device count). No notification body stored; metadata is pruned after 7 days.
Device - belongs to a user; receives pushes when subscribed to a channel.

What the server stores vs. your device

Data	Trigv cloud	Your device
API keys	Hashed only	-
Notification title & body	In-memory for delivery (not indexed)	Searchable local history (encrypted on device)
Event metadata	Status, level, timestamps, counts (deleted after 7 days)	Synced via push payload; kept in your local feed

Integration guides →API reference →