Partner-facing reference for /api/connectivity/v1, plus the Staylah-side key administration routes at /api/connectivity-keys.

Source of truth for this document:

routes/api/connectivity/pull.php — partners reading from Staylah
routes/api/connectivity/push.php — partners writing into Staylah
routes/api/connectivity/keys.php — our own key admin (not partner-facing)

0. Implementation status — read this first#

The contract below is final and stable. Most endpoints do not yet serve live data: they validate your payload fully and then return 501 with error.code = "not_implemented" and a details.pending string naming the service still being built.

Endpoint	Status
`GET /ping`	✅ Live
`GET /whoami`	✅ Live
Everything else	⚠️ Validates, then `501 not_implemented`

This is deliberate. You can build and certify against the real request contract today — a payload that passes validation now will pass validation when the data goes live, and nothing in your client changes on that day. A 501 is never returned for a request that would otherwise have failed validation; the 422 comes first.

Staylah Connectivity API

0. Implementation status — read this first#