Trigv home

Search docs

Getting started
  • Overview
  • How Trigv works
Help
  • Send test
  • API keys
  • Channels
  • Image attachments
Guides
  • All guides
  • cURL
  • Laravel
  • AI coding agents
  • Cursor
  • Claude Code
  • OpenAI Codex
  • Other agents
SDKs
  • All SDKs
  • JavaScript
  • Python
  • PHP
  • Go
  • Ruby
  • CLI
API reference
  • API overview
  • POST /api/v1/events
  • Errors & rate limits
  • API security
More
  • OpenAPI spec
Open in ChatGPT ↗ Ask questions about this page Open in Claude ↗ Ask questions about this page Open Markdown https://trigv.com/docs-md/learn/api-keys.md

API keys

API keys connect your tools to Trigv. You’ll need one for Zapier, GitHub Actions, scripts, and most integrations.

Step 1 — Open the dashboard

  1. Go to app.trigv.com and sign in.
  2. In the left sidebar, click API Keys.

Step 2 — Create a key

  1. Click Create API key (or similar).
  2. Give it a name you’ll recognize — e.g. Zapier, GitHub CI, Home server.
  3. Click create. Trigv shows the full key once.
  4. Copy it immediately and store it somewhere safe (password manager, GitHub secret, Zapier header).

You can’t view the full key again. If you lose it, rotate or revoke the old key and create a new one.

Step 3 — Use the key in your tool

Paste the key as a Bearer token — never in the message body:

Code
Authorization: Bearer trgv_abcd1234_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Each integration guide shows where to paste this (Zapier header, GitHub secret, etc.).

Managing keys later

Back in API Keys on the dashboard you can:

  • Rotate — invalidates the old key and gives you a new one
  • Revoke — permanently disables a key
  • Set expiry — optional, when creating a key

Good habits

  • Use separate keys per tool or environment (production vs. testing).
  • Never commit keys to git or paste them in public Zaps/screenshots.
  • Rotate immediately if you think a key leaked.

API security overview →

Previous Send test Next Channels

On this page

    Native push alerts for developers. Send alerts from webhooks, cron jobs, and scripts. We deliver alerts to your devices, but don't keep the message or notification history on our servers.

    Follow @trigvapp →

    Built by Harish Chouhan

    Product

    • Features
    • How it works
    • Pricing
    • Docs
    • Integrations
    • SDKs
    • API
    • Full LLMs text

    Company

    • About
    • Support
    • Changelog

    Legal

    • Terms & Conditions
    • Privacy Policy
    • Cookie Policy
    • API Security
    All systems ok. Get back to coding.

    © 2026 Webtions OU (dba Trigv)