Fire a trigger
POST/v1/projects/:project_id/triggers/:trigger_id/fire
Fires a trigger synchronously and returns the terminal firing record. The firing acts as the caller ∩ the trigger's policy_ids, which must allow starting the target, else the firing fails FORBIDDEN. A body carrying input or tool_context also needs the caller to start the target, else 403. The firing itself always settles here; an eval target's run is queued rather than executed inline, so the record names a queued run to poll.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 413
- 429
- 500
- 502
- 4XX
Terminal firing record
Bad request
Unauthorized
Forbidden
Trigger not found
Trigger inactive
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there