Appearance
Shell API
Helix Platform exposes a Cognito JWT HTTP API (not GraphQL):
| Host | Role |
|---|---|
https://api.platform.helix-dev.igentify.in | API Gateway HTTP API |
GET /auth/config | Public Cognito bootstrap |
/v1/{proxy+} | Authenticated shell routes (me, preferences, repos, catalog, installations, licenses, logs, notifications, push, …) |
Notifications
POST /v1/notifications creates an in-app notification (and can trigger Web Push). Body:
| Field | Purpose |
|---|---|
title, body | Required copy |
actionUrl | Optional deep link (e.g. Patch campaign or PR) |
actionLabel | Optional CTA label |
campaignId | Optional Patch campaign correlation |
Surface Apps (e.g. Helix Patch) use this for human gates after remediation sessions — Platform stays a shell; product logic stays in the app.
Iframe host bridge
Browser capabilities that must run in the top-level frame (notably Notification.requestPermission) are exposed via postMessage. See Host bridge.
Interactive reference: openapi.platform.helix-dev.igentify.in.
SSE for Log Center uses a separate Lambda Function URL (see stack output SseUrl).