Notifications
Partner-portal notification feed — the bell dropdown and `/notifications` page. Read state is tracked per portal user: one teammate marking a notification as read does not clear it for the rest of the team. Primarily a portal-session surface; API keys can read it with the `notification:read` / `notification:update` scopes.
x-cresora-status: planned in the canonical contract: they have no route on any host and return 404 (or 501 for reserved discriminator variants) until released. There is no separate preview stream, no feature flag to enable one, and no enrollment — the badge on each operation tells you whether it is served. See the stable /api/v1 reference for what you can call today. Like the stable API, these operations are server-to-server: there is no interactive console here. Download the preview spec (YAML).Config
Partner configuration — webhook URL, IP allowlist, HPP defaults, rate-limit tier, AVS decline policy. Read your own config; write via `PUT /config/partners/{partnerId}`. Rate-limit tier and AVS decline policy are Cresora-managed (admin-only); webhook URL, HPP settings, and IP allowlist are partner self-service.
Health
Service health and liveness probes — for partner integration monitoring and uptime dashboards. Unauthenticated endpoint.