Send alerts from code, no-code automations, webhooks, scripts, cron jobs, and AI agents to the Trigv mobile apps.
Create an account, install Trigv, create an API key, then run one command.
curl -X POST https://api.trigv.com/api/v1/events \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-H "Authorization: Bearer $TRIGV_API_KEY" \
-d '{"channel":"general","title":"Deploy finished","level":"success"}' import { Trigv } from "@trigv/sdk";
const trigv = new Trigv({ apiKey: process.env.TRIGV_API_KEY });
await trigv.sendEvent({
channel: "general",
title: "Deploy finished",
level: "success",
}); import os
from trigv import Trigv
trigv = Trigv(api_key=os.environ["TRIGV_API_KEY"])
trigv.send_event({
"channel": "general",
"title": "Deploy finished",
"level": "success",
}) client, err := trigv.NewClient(trigv.ClientConfig{
APIKey: os.Getenv("TRIGV_API_KEY"),
})
if err != nil {
log.Fatal(err)
}
_, err = client.SendEvent(context.Background(), trigv.SendEventRequest{
Channel: "general",
Title: "Deploy finished",
Level: trigv.LevelSuccess,
}) use Trigv\Client;
$trigv = new Client(['api_key' => getenv('TRIGV_API_KEY')]);
$trigv->sendEvent([
'channel' => 'general',
'title' => 'Deploy finished',
'level' => 'success',
]); require "trigv"
client = Trigv::Client.new(api_key: ENV.fetch("TRIGV_API_KEY"))
client.send_event(
channel: "general",
title: "Deploy finished",
level: "success"
) trigv send \
--channel general \
--title "Deploy finished" \
--level success
Accepted events return HTTP 202. See the event API reference for the
response and all fields.
Connect Trigv to the tools, scripts, and workflows you already use.
Set up Trigv, route alerts, and understand how delivery and privacy work.
Fire a test alert from the dashboard before wiring production scripts.
Create, rotate, and revoke workspace keys in the dashboard.
Route alerts by slug. Subscribe devices to the channels you care about.
Optional image_url for camera snapshots, charts, or screenshots.
What we deliver, what we store, and what stays on your device.
Key handling, logging policy, and how we protect your workspace.
HTTP contract, authentication, and machine-readable spec.