Skip to content
RelationsAI
Error codes

route_not_found

HTTP status
404
Retry
No
Execution
Nothing was done
Admin needed
No

Route not found. No operation exists at this path. Paths are case sensitive and resource names are plural and kebab-case.

What it means

The API returns HTTP 404 with error.code set to route_not_found. The default message is: "No such route."

Common causes

  • A typo in the path.
  • A missing /v1 prefix.

How to identify it

Check the response status (404) and error.code (route_not_found). Branch on error.code, not on the message text: messages can be reworded, codes do not change within v1. Log error.request_id (also sent as the X-Request-Id header) so support can find the request.

How to fix it

  • Compare the path with the API reference.

Retry guidance

Sending the request unchanged fails the same way. Fix the cause first (see How to fix it), then send it again.

Did anything happen?

This request was refused before any call was placed and before anything was charged.

Idempotency

Nothing was done and nothing was stored (under an Idempotency-Key, if you sent one), so the request can be sent again, with the same key if you used one, once the cause is fixed.

Who can fix it

The developer who sends the request can fix it; no administrator action is normally needed.

When to contact support

If the error persists after the steps above, contact support@relationsai.com. See Support for what to include (the request_id, the time in UTC, the operation, and whether you used a test or live key) and what never to send (API keys, Authorization headers, webhook signing secrets, recording links, transcripts or customer data).

Example error response

JSONJSON
{
  "error": {
    "code": "route_not_found",
    "message": "No such route.",
    "details": {},
    "request_id": "req_tbneaumpmazply5t4aveppsl",
    "retry": "no",
    "doc_url": "https://docs.relationsai.com/errors/route_not_found"
  }
}

See all codes in the error-code reference.

resource_not_foundmethod_not_allowed