Skip to main content
POST
Send a text document to your paired phone's Downloads folder (send_file)

Authorizations

Authorization
string
header
required

Opaque bearer token created on your paired Android phone. The format is rfk_live_ followed by 32 URL-safe alphanumeric characters (≥160 bits of entropy). Test tokens use the rfk_test_ prefix.

Body

application/json
filename
string
required

Destination filename, written into the phone's Downloads folder. Must end in an allowed plain-text/code extension (never .html/.svg — those render and execute if tapped) and be at most 120 characters after sanitization (rejected outright above 4096 raw characters). Path separators, control characters, and leading dots are stripped server-side and again on the phone before writing.

Example:

"runbook.md"

content
string
required

UTF-8 text content of the file. Non-empty, at most 131072 bytes.

Example:

"# Runbook\n\n1. Check the dashboard\n2. Page on-call if red\n"

Response

Created — the document was encrypted and dispatched to the phone.

document_id
string
required

Document id (doc_ prefix). The paired phone pulls the encrypted content with it via the FCM-nudged GET /v1/documents/{documentId} pull, never carried inline.

Example:

"doc_3f6e2a7c9b1d4f8e8a5b6c1d2e3f4a5b"

byte_length
integer
required

UTF-8 byte length of the content that was sent.

Example:

128