Skip to main content

Changelog

2026-08-19

  • Public API validation errors now include an actionable reason in the top-level message, while retaining the existing status codes and optional structured errors array
  • Identifier validation explains when a RemyPass _id is required and which endpoint supplies it
  • Unknown public API routes now return a JSON 404 response containing the attempted method and path
  • Internal API usage logs now record and display a sanitized failure reason for new failed requests; historical entries may not contain one
  • Existing successful v1 request and response contracts are unchanged

2026-05-05

  • Initial publication of RemyPass Developer Hub.
  • Added generated endpoint reference pages from api/docs/openapi.json.