Partner API

Organized care, from the files you already have.

Pharmacies, clinics, and labs already send families paperwork — fill records, lab results, discharge summaries. The Elderella Partner API lets you send that same material straight to the family's Elderella, where it becomes organized medications, appointments, and notes. One endpoint. The family stays in control the whole way.

Start the quickstart Read the API reference

How it works

Four steps take you from nothing to a file landing in a family's care records.

1. Get your credentials

   We issue you a client ID and secret. You exchange them for a short-lived token with the OAuth2 client-credentials grant. Authentication guide →

2. Ask the family for their elder's Elderella address

   Every elder in Elderella has a three-word address, like [email protected]. The family gives it to you the same way they'd give you a phone number. It's how you say who a file is for.

3. Request a connection

   You request a connection to that address. A primary caregiver approves it inside Elderella. You find out it's live through a webhook or by polling. Connections & webhooks →

4. Send files

   Once you're connected, send a file — a document, photo, audio, or text — and it flows into the family's care records. See it end to end →

The family is in control the whole way

This is the part that makes the API different from a normal upload endpoint, and it's deliberate.

• Nothing moves without consent. Until a primary caregiver approves your connection, you can't send anything to that elder. Approval happens inside Elderella, by the people who actually care for them.
• The address never confirms a person exists. Requesting a connection always looks the same from the outside, whether or not the address belongs to a real elder, and whether or not consent has been given. You can't use the API to probe who's in Elderella. This is a contract guarantee, held by tests — see the connection lifecycle.
• Consent can be withdrawn. A caregiver can revoke a connection at any time, and you'll be told. After that, your files stop flowing.

What you can send

The API takes one thing: a file about an elder. It doesn't care much what kind — a PDF of a discharge summary, a photo of a pillbox, an audio note, a plain-text message. Elderella's extraction pipeline reads it and turns it into structured care: medications, appointments, and notes the family can act on. Size and type limits are in the file guide.

Try it without touching real data

You don't need a real family to build your integration. Ask us for a test credential and you get a sandbox elder that auto-approves connections after about thirty seconds and accepts files without ever running extraction or touching anyone's real records. Rehearse the whole request → approval → send loop end to end, then flip to live. Sandbox & test mode →

Where to next