Instatus vs Trello

Instatus's REST API (`api.instatus.com`) lets a status-page owner script incident and maintenance updates, component status changes, and subscriber management for their own hosted status page. Every request must carry an `Authorization: Bearer <API_KEY>` header and a page ID from the dashboard, confirmed live via a 401 "API key is not sent in request header" response on an unauthenticated GET to `/v1/pages`; the same endpoint echoes a matching `access-control-allow-origin` on both a GET and a separate OPTIONS preflight sent with an Origin header, confirming the API is browser-callable. Instatus itself runs a permanent free-forever plan alongside paid per-project tiers, with no separate gate on API access.

Trello turns Kanban-style boards, lists, and cards into a scriptable project-management primitive, letting integrations create, move, and archive cards or attach webhooks that fire on board activity. Every account gets a free API key, and requests carry that key plus a short-lived member token as query parameters rather than a full OAuth redirect — a live unauthenticated call to `/1/members/me` confirms this by returning 401 'invalid key' rather than a bearer-token challenge (auth corrected OAuth -> API Key; OAuth1.0a exists only as an alternate authorization flow for third-party apps). Trello's Power-Ups marketplace and countless third-party integrations run on this same public API, available on every pricing tier including the free plan, and CORS is wide open — both the GET and an OPTIONS preflight echo `access-control-allow-origin: *`, resolving the stored 'unknown' value to yes.