Rate limits and auditability

Plan API traffic around this request window:

Route	Request window	Key
POST /api/v1/triggers/fire	30 requests per minute	Source IP

Requests may return 429 RATE_LIMITED when the window is exceeded. Back off before retrying. Trigger fan-out counts as one request regardless of subscriber count. Do not use API rate limits as a spending cap; configure your organization's budgets separately.

Trigger-fired sessions carry API source and the personal key owner's authority. Trigger Run history records the input, status, per-subscriber results, and duration; personal key usage updates its Last used value.

The API path is versioned under /api/v1. Clients should tolerate additional response fields.