Non-Root Endpoints Return 404

[ckarnes]

Every endpoint other than the root seems to return errorCode 40400.

I am running Obsidian in Debian 12. I installed both version 3.2 via the Community Plugins.

My vault is a single english word that is lower case and contains no spaces.

curl -X 'GET'   'http://127.0.0.1:27123/vault'  -H 'accept: application/json'   -H 'Authorization: Bearer <HIDDEN>'
{
  "message": "Not Found",
  "errorCode": 40400
}

curl -X 'GET'   'http://127.0.0.1:27123/'  -H 'accept: application/json'   -H 'Authorization: Bearer <HIDDEN>'
{
  "status": "OK",
  "manifest": {
    "id": "obsidian-local-rest-api",
    "name": "Local REST API",
    "version": "3.2.0",
    "minAppVersion": "0.12.0",
    "description": "Get, change or otherwise interact with your notes in Obsidian via a REST API.",
    "author": "Adam Coddington",
    "authorUrl": "https://coddingtonbear.net/",
    "isDesktopOnly": true,
    "dir": ".obsidian/plugins/obsidian-local-rest-api"
  },
  "versions": {
    "obsidian": "1.8.10",
    "self": "3.2.0"
  },
  "service": "Obsidian Local REST API",
  "authenticated": true,
  "certificateInfo": {
    "validityDays": 364.9992287037037,
    "regenerateRecommended": false
  },
  "apiExtensions": []
}

[coddingtonbear]

I'm afraid i'm not able to reproduce this. I recommend double-checking your requests by comparing them to the online documentation. I suspect your URL is subtly incorrect!

Reach out, though, if you continue to have this problem when using the online docs!

[ckarnes]

I have tried many of the endpoints in the interactive online documentation. Everything comes back empty. I am using the http endpoint and I played around with different host IP's: 0.0.0.0, 192.168.X.X. Still no joy. Thanks for looking into it.

[coddingtonbear]

I took a look at the request you captured and noticed it’s pointed at /vault (no trailing slash). In the interactive docs every example includes a trailing slash, so if those steps had run unchanged we’d expect to see /vault/ instead. When I intentionally drop the slash I get the same 404 you reported:

 $ http --verify=no --auth-type=bearer --auth=$APIKEY GET http://127.0.0.1:27123/vault
HTTP/1.1 404 Not Found
Access-Control-Allow-Origin: *
Connection: keep-alive
Content-Length: 50
Content-Type: application/json; charset=utf-8
Date: Wed, 18 Jun 2025 02:53:02 GMT
ETag: W/"32-7sGa9mMls5iy1fvTHPMlgbHZxYc"
Keep-Alive: timeout=5
X-Powered-By: Express
X-Response-Time: 0.640ms

{
    "errorCode": 40400,
    "message": "Not Found"
}

Running the exact request the the docs show and will actively execute if you use their interactive features—trailing slash included—returns a 200 OK and the files list:

HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Connection: keep-alive
Content-Length: 965
Content-Type: application/json; charset=utf-8
Date: Wed, 18 Jun 2025 02:53:00 GMT
ETag: W/"3c5-8CxaCSnIwbZlMhqnnOqMAk1Sdfk"
Keep-Alive: timeout=5
X-Powered-By: Express
X-Response-Time: 1.582ms

{
    "files": [
        "attachments/",
        "daily/",
        "discoveries/",
        "goals/",
        "how to/",
        "lists/",
        "memories/",
        "note-templates/",
        "people/",
        "permanent/",
        "planning/",
        "projects/",
        "reading notes/",
        "references/",
        "software/",
        "sources/",
        "temp.md",
        "templates/",
        "things/",
        "url notes/",
        "whiteboards/",
        "work/",
        "привет.md"
    ]
}

Are you really, really sure you tried the interactive docs (that is: used their interactive features) and found that they genuinely returned a 404?