API Overview

Memoreru API

The Memoreru API lets you access Memoreru data from external applications and scripts.

What You Can Do

• Create, get, update, and delete content: Manage pages, tables, slides, folders, and more programmatically
• Table row operations: Get, add, update, and delete row data (single or bulk via the same endpoint)
• Table column operations: Get, create, update, and delete table column definitions

---

API Documentation

Full endpoint specifications are available in the API Documentation, where you can view request/response formats, parameter details, and try out API calls.

Open API Documentation →

---

Requirements

The Memoreru API is available on Light plans and above. It's also available during the Feature Trial period.

---

Authentication

API authentication uses API keys. See "API Key Management" for how to generate keys.

---

Base URL

---

Endpoints

Content (common)

Get, update, and delete use the type-specific endpoints below (for example /contents/pages/{contentId}).
An ID that belongs to a different content type is treated as not found.

Folder

Page

Table

Slide

View

Graph

Dashboard

Screen

Report

Workflow

Password Protection

Webhooks

Extensions

For full endpoint details, see the API Documentation.

---

Response Format

• Successful responses use { "status": "success", "data": ... }. For table rows (GET /api/v1/contents/tables/{tableId}/rows?cursor&limit), set limit to the number of rows to retrieve. Omit cursor on the first request, then check pagination (limit, hasMore, and nextCursor) in the response
• When more rows are available, hasMore is true; pass the returned nextCursor as cursor in the next request. When hasMore is false and nextCursor is null, the list has ended
• Errors are returned as application/problem+json with a stable code. The full code list is in the Errors section at the end of the API documentation

---

Rate Limiting

API endpoints have rate limits. The default is 60 requests per minute.

When exceeded, a 429 Too Many Requests response is returned. Check the X-RateLimit-Remaining and Retry-After response headers for remaining quota and wait time.

---

Scopes

API keys can be configured with different scopes:

• Read + Write: All operations available (GET, POST, PATCH, DELETE)
• Read-only: Data retrieval only (GET)

Write operations (POST, PATCH, DELETE) with a read-only key return a 403 INSUFFICIENT_SCOPE error.