Changelog State API – Supabase Change History

Choose this endpoint when you specifically need the raw detected change event history for Supabase — individual change records with timestamps and types — rather than structured release summaries. Prefer this for change auditing, alerting pipelines, or when you need to filter by a specific change type like breaking_signal or version_changed. Use the sibling 'recent releases' endpoint if you want parsed, structured release notes instead of raw detection events.

• Vendor slug not found or not monitored — returns 404 or empty result set
• Invalid change type enum value — returns 400 validation error
• since parameter in wrong format — returns 400 date-time parse error
• limit out of range (0 or >200) — returns 400 validation error
• Payment not provided or insufficient — returns 402 Payment Required
• Upstream changelog source temporarily unavailable — may return 503 or stale data