FYInbox docs
Notification payload
Start with a title, then add severity, body, tags, metadata, event identity, timestamp, and safe link actions only when useful.
Fields
| Field | Required | Meaning |
|---|---|---|
| title | Yes | Short human-readable event summary. |
| body | No | Plain-text detail; it is never rendered as HTML. |
| severity | No | info, success, warning, error, or critical; defaults to info. |
| tags | No | Normalized labels; defaults to an empty list. |
| source | No | Descriptive producer label; it does not select key scope. |
| externalId | No | Identifier from the producing system. |
| deduplicationKey | No | Stable event identity used for safe create retries. |
| metadata | No | Bounded string key/value context for filtering. |
| actions | No | Up to five HTTPS or mailto link actions. |
| createdAt | No | Producer event time as an ISO 8601 date-time with offset. |
Validation and normalization
- The request is a strict JSON object; unknown fields are rejected.
- Title, tags, identifiers, and metadata keys are trimmed within their documented bounds.
- Tags are lowercased, converted to slugs, and deduplicated by normalized slug.
- Metadata keys are normalized to lowercase and collisions after normalization are rejected.
- Action IDs must be unique and at most one action may use the primary style.