> ## 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. # Schedule a reminder notification on your paired phone > Schedules a reminder — the `remind_me` MCP tool's backing endpoint. The phone (not the server) owns the schedule: the server encrypts the message once, delivers it to the paired phone immediately over FCM, and retains nothing (spec D3) — the phone arms a local alarm and fires the reminder notification at `at`. `at` is an absolute Unix epoch in **seconds**, and must be between 60 seconds and 365 days in the future (`400 fire_at_too_soon` / `400 fire_at_too_far`). The delivery to the phone is best-effort like any other push — a phone that never receives the setup message never arms the alarm. Requires a paired phone device on the account behind the bearer token (`409 no_phone_device`). **Phone-capability gate.** If the paired phone's reported app build is too old to schedule reminders, the request is refused outright (`426 phone_app_outdated`) rather than accepted and silently dropped on arrival — a later app update can't rescue a message that already arrived and was ignored. A phone that has never reported its version is allowed through instead, with a `warnings` entry naming the uncertainty. ## OpenAPI ````yaml /openapi.yaml post /v1/reminders openapi: 3.1.0 info: title: Reflecto API version: 1.1.0 description: >- The Reflecto public HTTP API lets you push notifications to your own paired devices — your Android phone and any browser extensions you've paired with it. Designed for the same job as Pushover or the old Pushbullet API: a single HTTPS call from a script, cron job, or webhook puts a notification on every screen you own. Authentication uses opaque prefixed bearer tokens (`rfk_live_…`) created and managed on your paired Android device — there are no email accounts, no passwords, no server-side user records beyond device pairing state. See the Authentication guide for the token lifecycle. The public-API surface is small on purpose: `POST /v1/send`, its capability-URL alias `POST /v1/send/{token}`, and a Pushover-compatible shim at `POST /v1/messages.json`. Mirroring traffic from your phone to your extension never reaches this surface — it stays end-to-end encrypted via the private `/v1/sync` SSE stream. See the Guides tab for the quickstart, authentication model, rate-limit contract, and encryption posture. contact: name: Reflecto url: https://github.com/reflectoapp/reflecto license: name: MIT url: https://github.com/reflectoapp/reflecto/blob/main/LICENSE servers: - url: https://api.reflecto.dev description: Production security: - BearerAuth: [] tags: - name: Send description: Push notifications to one or all of your paired devices. - name: Pushover compatibility description: >- Drop-in replacement for `POST https://api.pushover.net/1/messages.json`. Field names, request shape, and response shape mirror Pushover's so existing senders can migrate by changing a single URL. See [Pushover compatibility guide](/guides/pushover-compatibility) for the full mapping. paths: /v1/reminders: post: tags: - Reminders summary: Schedule a reminder notification on your paired phone description: >- Schedules a reminder — the `remind_me` MCP tool's backing endpoint. The phone (not the server) owns the schedule: the server encrypts the message once, delivers it to the paired phone immediately over FCM, and retains nothing (spec D3) — the phone arms a local alarm and fires the reminder notification at `at`. `at` is an absolute Unix epoch in **seconds**, and must be between 60 seconds and 365 days in the future (`400 fire_at_too_soon` / `400 fire_at_too_far`). The delivery to the phone is best-effort like any other push — a phone that never receives the setup message never arms the alarm. Requires a paired phone device on the account behind the bearer token (`409 no_phone_device`). **Phone-capability gate.** If the paired phone's reported app build is too old to schedule reminders, the request is refused outright (`426 phone_app_outdated`) rather than accepted and silently dropped on arrival — a later app update can't rescue a message that already arrived and was ignored. A phone that has never reported its version is allowed through instead, with a `warnings` entry naming the uncertainty. operationId: createReminder requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/CreateReminderRequest' examples: minimal: summary: 10 minutes from now value: message: Stand-up in 10 minutes at: 1786387000 responses: '201': description: Created — the reminder setup message was dispatched to the phone. content: application/json: schema: $ref: '#/components/schemas/CreateReminderResponse' examples: created: value: reminder_id: rmd_3f6e2a7c9b1d4f8e8a5b6c1d2e3f4a5b fire_at: 1786387000 createdWithWarning: summary: Created, but the phone's app version is unknown value: reminder_id: rmd_3f6e2a7c9b1d4f8e8a5b6c1d2e3f4a5b fire_at: 1786387000 warnings: - >- the paired phone hasn't reported its app version yet, so we can't confirm it supports this — it may be silently dropped if the installed build predates support '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '409': $ref: '#/components/responses/Conflict' '426': $ref: '#/components/responses/UpgradeRequired' '429': $ref: '#/components/responses/RateLimitedInteractions' security: - BearerAuth: [] components: schemas: CreateReminderRequest: type: object properties: message: type: string description: >- Notification text delivered when the reminder fires. 1–500 characters. example: Stand-up in 10 minutes at: type: integer description: >- Absolute Unix epoch SECONDS when the reminder should fire. Must be 60 seconds to 365 days in the future. example: 1786387000 required: - message - at CreateReminderResponse: type: object properties: reminder_id: type: string description: >- Reminder id (`rmd_` prefix). Pass it to `DELETE /v1/reminders/{id}` to cancel. example: rmd_3f6e2a7c9b1d4f8e8a5b6c1d2e3f4a5b fire_at: type: integer description: >- Unix epoch seconds the reminder is scheduled for (echoes the requested `at`). example: 1786387000 warnings: type: array items: type: string description: >- Present when the phone hasn't reported an app version yet, so the server can't confirm it supports reminders — the setup message may be silently dropped if the installed build predates support. Omitted entirely once the phone's reported version is known to support it. example: - >- the paired phone hasn't reported its app version yet, so we can't confirm it supports this — it may be silently dropped if the installed build predates support required: - reminder_id - fire_at ErrorResponse: type: object properties: error: type: object properties: code: type: string example: message_too_long message: type: string example: message must be ≤ 1500 bytes details: type: object additionalProperties: {} required: - code - message required: - error SimpleErrorResponse: type: object properties: error: type: string example: invalid_token message: type: string required: - error description: >- Flat error shape used for auth failures — `invalid_token` carries only the stable code; `missing_token` adds a `message` hint pointing at the `Authorization: Bearer …` header. The `message` field is therefore optional. responses: BadRequest: description: Malformed payload or invalid field value. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: invalidPriority: value: error: code: invalid_priority message: priority must be one of min, low, default, high, urgent messageTooLong: value: error: code: message_too_long message: message must be ≤ 1500 bytes details: bytes: 1620 max: 1500 invalidFilename: summary: POST /v1/documents — blocked extension or unsafe name value: error: code: invalid_filename message: >- filename must end in an allowed extension and be a safe name (max 120 characters) invalidContent: summary: POST /v1/documents — empty content value: error: code: invalid_content message: content must not be empty Unauthorized: description: Missing, invalid, or revoked bearer token. content: application/json: schema: $ref: '#/components/schemas/SimpleErrorResponse' examples: missingToken: value: error: missing_token message: 'Authorization: Bearer rfk_live_… required' invalidToken: value: error: invalid_token Forbidden: description: Token exists but lacks scope for the requested action. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: priorityCapped: value: error: code: priority_capped message: Token's priority_cap is 'default'; requested 'high' Conflict: description: The request conflicts with the current state of a resource. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: noPhoneDevice: summary: Owner has no paired phone to ask value: error: code: no_phone_device message: no_phone_device UpgradeRequired: description: >- The target phone's Reflecto app is too old to receive this — update Reflecto on the phone from the Google Play Store before this can be delivered. Nothing was sent. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: phoneAppOutdated: value: error: code: phone_app_outdated message: >- the paired phone's Reflecto app is too old to receive this — update Reflecto on the phone from the Google Play Store before this can be delivered; nothing was sent. RateLimitedInteractions: description: >- Rate limit or resource cap exceeded. For interaction creation this includes the 10-pending-per-owner cap; for ring and reminders, IP/token rate limits. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: rateLimitExceeded: value: error: code: rate_limit_exceeded message: Rate limit hit tooManyPending: summary: Owner already has 10 pending interactions value: error: code: too_many_pending message: too_many_pending securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: rfk_live_… description: >- 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. ````