cURL
Send a test alert from your terminal — handy if you’re comfortable with the command line and want to verify Trigv before wiring Zapier or a script.
Before you start
- Install Trigv for iOS from the App Store and sign in on your phone (Android coming soon).
- Create an API key at app.trigv.com → API Keys (guide).
- Or try Send test first if you prefer no terminal.
Step 1 — Run this command
Replace trgv_YOUR_KEY_HERE with your 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_HERE" \
-d '{"channel":"general","title":"Hello from curl"}' Step 2 — Check the result
- HTTP
202— event accepted and queued. Check your phone. - HTTP
200— duplicateidempotency_key(same event returned). 401— wrong or missing API key.404— channel slug doesn’t exist in your workspace.- See errors & rate limits for the full list.
Richer example
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_HERE" \
-d '{
"channel": "general",
"title": "Deploy finished",
"description": "Build completed successfully",
"level": "success"
}' Common mistakes
- Putting the API key in the JSON body — use the
Authorizationheader only. - Wrong channel slug — must match a channel in your workspace exactly.
- Phone not subscribed to the channel — event sends but no device receives it.