REST API

Base URL

https://api.memside.com

Authentication

Authorization: Bearer mem_sk_your_key_here

Do not send API keys in query strings.

Available routes

Method	Path	Purpose
`GET`	`/context/startup`	Load startup context.
`GET`	`/context/resume`	Continue from a checkpoint.
`GET`	`/context/workspace-profile`	Load workspace guidance.
`GET`	`/memories`	List Memories.
`GET`	`/memories/search`	Search Memories.
`GET`	`/memories/{id}`	Get one Memory.
`GET`	`/memories/batch`	Get several known Memories.
`POST`	`/memories`	Create a Memory.
`PATCH`	`/memories/{id}`	Update a Memory.
`DELETE`	`/memories/{id}`	Delete a Memory when allowed.

Search example

curl "https://api.memside.com/memories/search?q=weekend%20trip&limit=5" \
  -H "Authorization: Bearer $MEMSIDE_API_KEY"

Create example

curl https://api.memside.com/memories \
  -X POST \
  -H "Authorization: Bearer $MEMSIDE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Weekend trip plan\nHotel confirmed. Choose activities next.",
    "type": "note",
    "sensitivity": "private",
    "tags": ["travel", "planning"]
  }'

Common status codes

Status	Meaning
`200`	Request succeeded.
`201`	A resource was created.
`400`	The request is invalid.
`401`	Credentials are missing or invalid.
`403`	Access is not allowed.
`404`	The resource was not found.
`429`	Too many requests.
`500`	Server error.

Error response

{
  "ok": false,
  "error": {
    "code": "unauthorized",
    "message": "Missing credentials",
    "status": 401,
    "retryable": false
  }
}

App-only features

The public API is intentionally smaller than the Memside app. Account management, billing, private file access, and other app-only features are not general API-key routes.

Secret Memories are excluded from public API-key access.

Source and examples

Next steps