Skip to main content

not_found

Either the URL matches no route, or the id in it matches no record your key can see. Nothing was created, sent or charged.

Status: 404

{
  "status": 404,
  "type": "not_found",
  "message": "No such endpoint. Every path is served under /v1.",
  "request_id": "req_01J8K2P...",
  "doc_url": "https://docs.epostix.com/errors/not_found"
}

message varies: No such endpoint for an unknown path, the wording above when the version prefix is missing, and a record message such as Email not found when the path is fine.

Why you got this​

  • The URL has no /v1 prefix. The base URL is https://api.epostix.com/v1, so /emails is not a route and /v1/emails is. This is the most common first mistake.
  • The path is misspelled, or pluralised differently from the reference.
  • The id belongs to a record that was deleted, or that was never created.
  • The id belongs to another workspace. That returns 404 rather than 403 deliberately, so the API never confirms whether an id exists outside your own workspace.

How to fix it​

Compare the full URL against the base URL, prefix included, before you look at anything else. If the path is right, the id is the problem: check it against the same workspace the key belongs to.

Some resources have their own type, which tells you the path was correct: domain_not_found, template_not_found and attachment_not_found. A real path called with the wrong verb returns method_not_allowed.

Is it safe to retry​

No, not unchanged. The same URL keeps returning 404. Fix the path or the id and send a new request. Nothing was stored, so reusing the same Idempotency-Key is safe.