Pharos / Docs / v0.5.10

Migrating from Cachet 2.x

Updated 2026-09-08 · Pharos 0.5.10

Three things are deliberately identical, so existing scripts survive:

• GET /api/v1/components — same path, same envelope, same field names.
• Status integers — 1 operational, 2 degraded, 3 partial, 4 major. Pharos adds 5 for maintenance.
• X-Cachet-Token is accepted everywhere Bearer is, and POST works as an alias for PUT on a component.

What needs editing:

• Creating incidents. Cachet took an integer status and a single component; Pharos takes a status name and a components object.
• Endpoints that do not exist here — component groups, metrics, subscribers, actions, ping, version, and fetching or deleting a single incident.
• No pagination parameters. Components return in one page; incidents are capped at the 50 most recent.
• No importer. Moving existing data across means writing it in through the API. The matching status integers are what make that straightforward.