Summary
I'm trying to build a direct integration between Omi and Obsidian using an MCP API key. Testing against the REST API I'm seeing the following responses:
| Endpoint |
Response |
GET https://api.omi.me/v1/memories |
404 Not Found {"detail":"Not Found"} |
GET https://api.omi.me/v2/memories |
404 Not Found {"detail":"Not Found"} |
GET https://api.omi.me/v1/conversations |
401 Unauthorized {"detail":"Invalid authorization token"} |
All requests use Authorization: Bearer omi_mcp_... with a valid MCP key created in the Omi app (Settings → Developer → MCP → Create Key).
Questions
- Are
/v1/memories and /v2/memories deprecated or moved? If so, what are the current REST endpoints for fetching memories?
- Are MCP keys (
omi_mcp_...) valid for direct REST API calls, or is a separate key type required?
- Is there up-to-date public API documentation covering the current endpoint structure and authentication?
Context
The MCP/SSE integration works correctly for Claude Desktop. However I'd like to pull memories and conversations programmatically into Obsidian on a schedule. The community plugin atomicpapa/obsidian-omi-sync fails with the same 401/404 errors — so this likely affects anyone trying to build on the REST API with MCP keys.
Happy to test anything or provide more detail if helpful.
Summary
I'm trying to build a direct integration between Omi and Obsidian using an MCP API key. Testing against the REST API I'm seeing the following responses:
GET https://api.omi.me/v1/memories{"detail":"Not Found"}GET https://api.omi.me/v2/memories{"detail":"Not Found"}GET https://api.omi.me/v1/conversations{"detail":"Invalid authorization token"}All requests use
Authorization: Bearer omi_mcp_...with a valid MCP key created in the Omi app (Settings → Developer → MCP → Create Key).Questions
/v1/memoriesand/v2/memoriesdeprecated or moved? If so, what are the current REST endpoints for fetching memories?omi_mcp_...) valid for direct REST API calls, or is a separate key type required?Context
The MCP/SSE integration works correctly for Claude Desktop. However I'd like to pull memories and conversations programmatically into Obsidian on a schedule. The community plugin
atomicpapa/obsidian-omi-syncfails with the same 401/404 errors — so this likely affects anyone trying to build on the REST API with MCP keys.Happy to test anything or provide more detail if helpful.