Status, ledger, and sync
Check reachability, inspect local-to-remote mappings, and observe remote bookings.
Connector status
The panel polls /api/connectors/status for the first connector currently used by any transport. A configured ping endpoint performs the remote check; without one, the connector reports ready after local configuration is validated.
| Field | Meaning |
|---|---|
configured | Whether the connector can be constructed with its current config and secrets |
ok | Whether its ping succeeded |
status | Optional remote HTTP status |
checkedAt | Time of the status response |
Mapping ledger
Each connector gets a local ledger under .praxis/connectors/<id>.json. It maps profile ids to remote actor ids and appointment ids to remote booking ids, then remembers remote bookings seen during observation.
The public ledger route returns counts rather than exposing the id maps themselves.
Booking observation
If bookings.path is configured, Praxis can list the remote records and mark newly observed ids. Observation is read-only against the remote system.
Request a page of remote bookings with optional status filtering.
Check ids against the connector ledger.
Add fresh ids and update lastSyncedAt locally.
Return observed and skipped counts plus remote metadata.
Default connector
Connector routes accept an explicit id. When it is omitted, Praxis uses the first connector in config/connectors.json. Pass the id in scripts and production diagnostics to avoid relying on file order.