HTTP API
Base URL:
- Cloud:
https://api.trigora.dev - Local:
http://localhost:3477whiletrigora devis running
Cloud requests send Authorization: Bearer <TRIGORA_TOKEN>. Optional X-Trigora-Project-Id selects a project. If you omit it, the workspace default project is used.
Local trigora dev starts with a default project and does not require a bearer token. Projects created through POST /v1/projects are persisted in the local SQLite state.
Local trigora dev implements the developer runtime subset of /v1. whoami, trigger management and firing, billing, and usage remain Cloud-only. trigora dev does not serve GET /v1/whoami.
The local deploy API can store and version Program artifacts. Deployed artifacts with no effect bundle can run directly. trigora dev does not execute uploaded Cloud effect bundles; effectful local Programs should be discovered from project source and run through the normal local development path.
Routes
Section titled “Routes”| Method | Path | Purpose |
|---|---|---|
GET | /v1/whoami | Token’s workspace |
GET, POST | /v1/projects | List or create projects |
POST | /v1/programs/deploy | Upload a compiled Program |
GET | /v1/programs | List Programs |
GET | /v1/programs/:id | One Program |
GET | /v1/programs/:id/versions | Versions |
GET | /v1/programs/:id/triggers | Triggers for one Program |
PUT | /v1/projects/:projectId/triggers | Replace the project’s trigger list |
POST | /v1/executions | Start. Body { programId, input? } |
GET | /v1/executions | List |
GET | /v1/executions/:id | Inspect |
POST | /v1/executions/:id/events | Body { name, payload? } |
POST | /v1/executions/:id/cancel | Cancel |
GET | /v1/executions/:id/result | { status, result?, error? } |
List routes accept limit and cursor.
Webhook ingress is a separate host, with no workspace token:
| Method | Path | Purpose |
|---|---|---|
POST | https://hooks.trigora.dev/:publicId | Start the Program for that webhook trigger. Body is the Program input. 202 returns { executionId }. |
See Triggers.
Workspace, billing, and usage routes exist under /v1/workspaces/*, /v1/billing/*, and /v1/usage. The CLI does not wrap every billing call. Metering is described in Usage & billing.
Errors are JSON { "error": { "code", "message" } }. See Errors.