onelifevibe

Platform API error

not_found

not_found is the HTTP 404 the Platform API returns when the route, event or subscription you addressed does not exist for your key.

Updated November 6, 2026

HTTP status
404
Code
not_found
API
Platform API v1

Returned when

What to do

Example answer

HTTP/1.1 404
content-type: application/json

{
  "error": {
    "code": "not_found",
    "message": "No route <METHOD> <path>."
  }
}

Related errors

What it means

The Platform API answers HTTP 404 with code not_found when the thing you addressed does not exist for your key. Three kinds of target fall under this: a path under /api/platform/v1, an event id, and a subscription.

Every error arrives in the same envelope: {"error":{"code":"…","message":"…","hint":"…"}}. The code is stable and safe to branch on. The message is written for a person reading logs and can change, so do not parse it.

Why you are seeing it

The first case is an unknown path under /api/platform/v1 — a typo in the version segment, a missing resource name, or a route that lives on a different API. The message reads No route <METHOD> <path>.

The second case is an event id that sits outside the worlds your key covers. This is deliberate: an event outside your worlds answers 404 on purpose, so ids never leak across clients. The message reads No such event for this key. A 404 here tells you nothing about whether the event exists anywhere else.

The third case is a subscription that belongs to another client or was deleted. The message reads No such subscription.

How to fix it

Start with GET /api/platform/v1, which lists every endpoint. Compare the method and the full path you send against that list, including the version prefix and any id in the path.

For events, check that the id was issued to a world your key covers. If you are testing with ids copied from another client's data, expect 404 by design and switch to an id from your own worlds.

For subscriptions, check the id against the client that created it. If the subscription was deleted, the record is gone; create a new one rather than retrying the old id.

Handling it in code

Branch on the code field, not on the message. You may see No route <METHOD> <path>., No such event for this key., or No such subscription. Treat all three as not_found and log the message alongside your request details so support can read it later.

Pass the hint through to whoever reads the error. Catching 404 as a generic HTTP failure hides the difference between a wrong route and an event outside your key's worlds, and those two need different fixes. Retrying an unchanged request returns the same answer, so correct the request or the resource instead of looping.

If you also work with tool names, unknown_tool is the related code listed for this one; check it when a name rather than a path is the problem.

Questions

What does not_found mean on the OneLifeVibe Platform API?

It is the code returned with HTTP 404 when the route, event or subscription you addressed does not exist for your key. The body carries code, message and hint fields so you can see which of those three cases applies.

Why does an event I know exists return 404?

An event outside the worlds your key covers answers 404 on purpose, so ids never leak across clients. Confirm the id was issued to a world your key can read instead of retrying the same request.

Should I match on the error code or the message?

Match on code. Codes are stable, while messages such as No route <METHOD> <path>. and No such subscription. are meant for logs and support rather than control flow.

Keys, plans and usage live in the console: rotate keys, add webhook endpoints, see the last 30 days.

Open the console Plans

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.