Public Document API reference · mansoq-im-wrapper

Declared route and availability

This resource is declared in mansoq-im-wrapper at /api/{installed_plugin_prefix}/public/documents/{token}/. plugin/local mount; actual prefix and enablement require deployment verification A registered path and an indexed handler do not prove deployment availability, user permission or production readiness.

Operation map

public_document · ANY

Missing, invalid, expired, and unknown-kind tokens all 404 identically -- a caller learns nothing from the difference, including whether a token ever existed.

Rate-limited per token rather than per client IP: behind a reverse proxy every request shares one REMOTE_ADDR, so an IP-keyed limit is really a single global one. The token is 256 bits, so guessing is not the threat; capping reuse of a forwarded link is.

ANY /api/{installed_plugin_prefix}/public/documents/{token}/ — action public_document. static function declaration extracted; request/runtime review pending.

Path and deployment-context parameters:

Authorization: no literal permission name was resolved in the bounded handler/helper traversal. Authentication, inherited policies, object/facility scoping and middleware still require review; this does not mean public access.

Explicit response statuses in observed code: 429. Other branches/framework exception handling may differ.

Integration review checklist

Confirm the installed route and full schema; review authentication, organization/facility scoping, all accepted fields, value-state and date/time semantics, idempotency, pagination, response/exception branches and the allowed correction/reversal workflow. Test positive and negative cases with synthetic data. This source reference does not establish external certification or replace an illustrated user procedure.