Convenience alias for POST /v1/send where the bearer token is the last path segment instead of the Authorization header. Useful in environments that cannot set custom headers (basic IoT devices, simple shell pipelines).
Path-token requests have their URL redacted before any access log write. The header form is still the canonical/preferred way to call the API — path-tokens are easier to leak via shell history, screenshots, and referrers.
Documentation Index
Fetch the complete documentation index at: https://docs.reflecto.dev/llms.txt
Use this file to discover all available pages before exploring further.
Reflecto sender token (rfk_live_… or rfk_test_…).
^rfk_(live|test)_[A-Za-z0-9]{32}$"rfk_live_aB3xQ7mN9pK2vR5tY8uW4sZ1cE6dF0gH"
Canonical send payload. Form-encoded and text/plain bodies are documented in the guides — the server normalises them to this shape.
Notification body. Required. 1–1500 bytes (UTF-8). maxLength is omitted from the schema because JSON Schema measures characters, not bytes — server enforces a byte cap to keep the 2 KB envelope budget honest across CJK / emoji content.
1"Backup finished in 12m"
Headline rendered above the body. 1–100 bytes (UTF-8). Schema omits maxLength because JSON Schema measures characters, not bytes.
1"Backup"
Notification priority. min/low use normal FCM; rest use high.
min, low, default, high, urgent "default"
Up to 5 tags rendered as labels. Oversize / overcount entries are truncated with a warning rather than rejected — maxItems is deliberately omitted so SDK generators don't client-side-reject valid-but-overcount inputs that the server will accept and trim.
Tag string. Oversize / overcount entries are truncated with a warning rather than rejected.
Clickable URL attached to the notification. http(s) only, ≤ 512 bytes.
"https://example.com/backup/123"
Display text for url. ≤ 32 bytes (UTF-8). Schema omits maxLength because JSON Schema measures characters, not bytes.
"View report"
Up to 3 action buttons. Each button opens its url when tapped. Overcount entries are truncated with a warning — maxItems is deliberately omitted so SDK generators don't client-side-reject.
Target device(s). all (default), mobile (alias phone), desktop, or a comma-separated list of device labels. Unknown labels become warnings.
256"all"
Render the body as Markdown on the extension. Ignored on Android in MVP.
false
Seconds the message stays in the per-device queue if not delivered live. Out-of-range values are silently clamped to the [0, 259200] range (72 hours, matching the Redis queue TTL).
0 <= x <= 259200259200