curl --request POST \
--url https://api.reflecto.dev/v1/send \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"message": "Backup finished in 12m"
}
'{
"id": "msg_3f6e2a7c9b1d4f8e8a5b6c1d2e3f4a5b",
"delivered_to": [
{
"device_id": "dev_9af3",
"type": "android",
"delivery": "push"
},
{
"device_id": "dev_2bc1",
"type": "extension",
"delivery": "push"
}
],
"warnings": []
}Send a notification to your paired devices
Sends a notification to one or every paired device for the user behind the bearer token. Accepts JSON, form-encoded, or text/plain bodies. When the body is text/plain (or has no Content-Type), the entire body becomes the message field.
Total serialized envelope size is hard-capped at 2048 bytes. Requests over that limit return 413 payload_too_large before any rate-limit counters are charged.
Unknown device labels in the device parameter are surfaced as warnings, not errors — long-running cron jobs do not break when a device is unpaired.
curl --request POST \
--url https://api.reflecto.dev/v1/send \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"message": "Backup finished in 12m"
}
'{
"id": "msg_3f6e2a7c9b1d4f8e8a5b6c1d2e3f4a5b",
"delivered_to": [
{
"device_id": "dev_9af3",
"type": "android",
"delivery": "push"
},
{
"device_id": "dev_2bc1",
"type": "extension",
"delivery": "push"
}
],
"warnings": []
}Authorizations
Body
Canonical send payload. Form-encoded and text/plain bodies are documented in the guides — the server normalises them to this shape.
Notification body as plain text — write quotes and newlines literally, never JSON-escape them (no " or \n sequences; the JSON layer handles encoding). 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"
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.
Target device(s). all (default), mobile (alias phone), pc (every computer — browser extension, web app, CLI and desktop app), desktop (the native desktop app only), a comma-separated list of device labels, or an exact device id. Labels are not unique — one shared by two devices delivers to both, so pass an id to reach exactly one. all, mobile, phone, pc and desktop are reserved: a device you have NAMED after one of them is not reachable by that name, only by its id. An unknown label becomes a warning and falls back to delivering everywhere; a reserved word that matches none of your devices delivers to nobody and says so in warnings.
256"all"