// Client error

404 Not Found

The server did not find a current representation for the target resource, or chooses not to disclose that one exists.

Common causes

The path is incorrect.
The resource identifier does not exist.
The route is deployed under another base URL or version.
Authorization policy hides resource existence.

Troubleshooting

Compare the final URL with the documented server and path.
Check path parameter encoding.
Confirm the resource exists in the current environment.
Do not retry unchanged requests indefinitely.

Example response

HTTP/1.1 404 Not Found
Content-Type: application/json

{ "code": "payment_not_found", "id": "pay_123" }

Related status codes

400 Bad Request 401 Unauthorized 422 Unprocessable Content

// GET STARTED

Inspect the complete API response.

Use REST Test to send a request and review its status, headers, timing and body together.