API Docs / Scalar Access

Where to find the public Trigify API docs, how access works, and how the API ties into MCP and the CLI.

The Trigify REST API is the canonical programmatic surface. The same API powers the dashboard, the CLI, MCP, and Jarvis, so anything you can do in the app you can ultimately do via the API.

Where the docs live

API reference is hosted at the Trigify API docs site (linked from Settings → API Keys in the app). The docs moved off Mintlify onto Scalar; bookmark the link from inside the app rather than relying on older URLs.

Access

  • API access is key-gated — every protected endpoint requires a valid API key passed as the x-api-key header. Missing or invalid keys return 401.
  • Keys are created and revoked from Settings → API Keys.
  • API usage is billed in the same credit model as in-app usage; there is no separate API plan tier.

What's covered

The REST API covers the full Trigify surface, including:

  • Per-source search creation across X, Business Network, Reddit, Substack, YouTube, Hacker News, Podcasts, and other supported sources.
  • Search results retrieval.
  • Workflow operations.
  • Custom signal ingestion.

The OpenAPI spec is kept in sync with the live API, so generated clients should track current behaviour.

API, MCP, and CLI relationship

  • REST API — direct HTTP access. Use when you're building your own integration or generating a client.
  • MCP — https://api.trigify.io/mcp. Use when your agent or harness speaks MCP natively (e.g. Claude Desktop, Claude Web via OAuth, Claude API via your Trigify key).
  • CLI — terminal client. Use for scripting, scheduled jobs, and agent harnesses that prefer terminal tools.

Status codes you'll see

  • 200 — success.
  • 401 — missing or invalid API key.
  • 403 — key valid but lacking permission for the resource.
  • 404 — resource not found.
  • 429 — rate limited; back off and retry.

Related articles