Skip to main content

public-api-not-found

Type URI: https://developer.risepeople.com/errors/public-api-not-found HTTP status: 404 Not Found Format: application/problem+json (RFC 7807)

When this fires​

The URL you requested doesn't match any route registered under the Public API. Most likely:

  • Typo in the path — wrong resource name, wrong pluralization, missing or extra segment.
  • Wrong API version — only /v1 is currently published; older or experimental versions return 404.
  • Internal endpoint — an endpoint exists internally but isn't exposed through the public API.
  • Trailing-slash mismatch — /v1/employees/ vs /v1/employees. Drop trailing slashes.

This is distinct from a per-endpoint resource lookup miss (e.g. GET /v1/employees/unknown-id), which returns the standard not_found code from the endpoint itself — see Standard errors.

Example response​

{
  "type":   "https://developer.risepeople.com/errors/public-api-not-found",
  "title":  "Not Found",
  "status": 404,
  "detail": "No public API route matches GET /v1/employess.",
  "instance": "/v1/employess"
}

How to fix it​

  1. Check the URL against the API Reference. Resource names are plural, snake_case, and use /v1/ as the version prefix.
  2. Make sure you're hitting https://api.risepeople.com — not the developer portal or a sandbox host.
  3. Drop trailing slashes unless the endpoint explicitly requires them.
  4. If you're sure the endpoint should exist but you're getting 404, quote the X-Request-Id from the response in a support ticket.