Getting Started
Understand the Memo API environment, request format, and recommended integration workflow.
The Memo API is a REST API for the data and workflows used by ANABOX smart. Production requests use this base URL:
https://api.memo.wirewire.de/v1Paths in the generated reference are relative to that URL. For example, GET /organizations/ becomes:
https://api.memo.wirewire.de/v1/organizations/Before you begin
You need:
- A Memo account with access to the organization you want to integrate.
- An API key created in Memo account settings, or a valid Memo JWT bearer token.
- The IDs of the organization and patient records you intend to use.
Use API keys for server-to-server integrations. Keep browser-only calls behind your own backend because keys must not be embedded in frontend code and browser origins are subject to the API's CORS allowlist.
Recommended request flow
Start with read operations before writing data:
- Call
GET /accounts/currentto verify the credential. - Call
GET /organizations/to find the accessible organization. - Call
GET /users/?organization=...to find patients and other users. - Read medications, calendar entries, or devices using the relevant organization or patient ID.
- Add write operations only after the read path and authorization scope are correct.
This order catches most credential, tenancy, and ID problems without changing production data.
API areas
| Area | What it represents |
|---|---|
| Accounts | The authenticated Memo identity and account metadata |
| Organizations | The tenant boundary for users and clinical data |
| Users | People in an organization; a patient is represented by a user record |
| Medications | Organization-owned medication records |
| Calendars | Medication schedule entries and finalized time windows |
| Devices | Registered devices, connectivity, alarms, case state, and events |
| Server-side PDF generation from an allowed URL |
Schema and environments
The API Reference is generated from the Memo OpenAPI document. This documentation repository includes a schema snapshot so production builds are repeatable. Maintainers can point the site at another environment during development:
OPENAPI_JSON_URL=http://localhost:5002/openapi.json yarn devThe production schema is also available at api.memo.wirewire.de/openapi.json.