Sign up and get your API key
Create your account, set up a workspace, and grab your API key from the dashboard. We only store a secure hash.
HOW IT WORKS
First alert in minutes, not hours.
Sign up, grab your API key, and connect Trigv to your code or tools. If you can copy-paste curl, you're basically done. Here's the whole flow, start to finish.
Download the app and pick channels
Get Trigv on iOS or Android. Join your workspace, choose the channels you care about, and allow notifications.
Connect your code or tools
POST an event from your backend, cron job, script, or tool. Your phone gets the alert. You keep building.
DOWNLOAD
Get Trigv on your phone.
The app is where your alerts land. Grab it, join your workspace, and pick what you want to hear about.
- Sign in with your Trigv account
- Join your workspace
- Pick the channels you care about
- Allow notifications
macOS app — coming soon
ALERT TYPES
Notification types.
Tag events as info, success, warning, or error so every alert is clear on your lock screen and in your feed.
Staging's alive 🧪
Someone paid 🤑
Cron still going 🐢
prod cried() 💀
TRY IT
See the curl → phone flow.
POST an event, watch the terminal return 202 Accepted, and imagine your phone lighting up a second later.
Shipped to prod 🚀
Stripe pinged 💸
curl -X POST https://api.trigv.com/api/v1/events \
-H "Authorization: Bearer trgv_…" \
-H "Content-Type: application/json" \
-d '{
"channel": "deploys",
"title": "Deploy finished",
"description": "Build #42 passed",
"level": "success"
}' WHAT YOU SEND
One JSON body. A handful of fields.
POST to /api/v1/events with your key in the Authorization header. Two fields are required; the rest are optional.
| Field | Required | What it does |
|---|---|---|
channel | Yes | Channel slug the alert routes to — e.g. deploys. |
title | Yes | Push headline. Stored on your device only. |
description | Optional | Body text. Falls back to the title if omitted. |
level | Optional | info, success, warning, or error — sets the color. |
delivery_urgency | Optional | standard or time_sensitive to break through Focus. |
image_url | Optional | Optional HTTPS image. Passed through, never stored. |
url | Optional | Optional destination link (PR, deploy, payment). Passed through, never stored. |
idempotency_key | Optional | Dedup key for safe retries from CI and cron. |
HTTP 202 Accepted
{
"event": {
"status": "queued",
"level": "success",
"target_device_count": 2
}
}Title and body never appear in the response — they're delivered to your device, not stored on our servers. No click-through URL field; keep the link in the body.
INTEGRATIONS
If it can POST, it can ping your phone.
No SDK to install. Wire Trigv into the tools you already run — each guide has copy-paste setup.
PRIVACY
Your alerts stay yours.
We deliver the notification, then forget the words. The searchable history lives on your phone.
What the server keeps
- Event status, level, and timestamps
- Channel and workspace IDs
- Monthly usage counter for billing
What stays on your phone
- Notification title and body
- Searchable local history
- Encrypted app sandbox storage
GET STARTED
Send your first alert today.
Create a workspace, grab a key, and POST. You'll feel the first ping in minutes.