Resource Not Found

← Back to Overview

This error occurs when the requested resource path does not exist, or the requested single record (by its primary key/ID) does not exist in the database.

[!NOTE] For security reasons, the platform will also return a 404 Not Found (rather than a 403 Forbidden) if a user tries to access a private record that they do not own.

---

Error Response Example (RFC 9457)

{
  "type": "https://docs.apinow.app/errors/not-found",
  "title": "Resource Not Found",
  "status": 404,
  "code": "RESOURCE_NOT_FOUND",
  "detail": "Route not found: GET /api/v1/nonexistent",
  "instance": "/api/v1/nonexistent"
}

---

Troubleshooting Guide

For API Consumers (What it means & how to fix)

• Invalid Endpoint URL: Verify that the URL path, collection name, and resource ID are correct and matches the API’s documentation.
• Private Data Ownership: If you are trying to access a specific record ID and receive a 404, check if the record was created by another user. You may only access records that belong to your account or company.

For API Authors (Domain & API Modeler notes)

• Collection Exposure: In the API Modeler, verify that the target entity is exposed and that the route path matches.
• Ownership Access Rules: If a Match Resource Owner Access Rule is active on the exposed entity, the Serverless Engine will automatically hide records that do not belong to the authenticated user. Ensure your testing user owns the record or disable the rule for public reading.