Recipient Portal
Render the recipient-portal login page
Public endpoint that returns client + program branding for the recipient-portal login page. If session_id is omitted a fresh Redis-backed session is created and returned (1-hour TTL). The recipient portal does NOT use bearer tokens — it identifies the visitor through the {session_id} URL path parameter that is then carried through every subsequent recipient-portal call.
GET
Render the recipient-portal login page
Path Parameters
Client (tenant) the recipient belongs to.
Example:
207
Program id, or none/0 for general (non-program-scoped) login.
Example:
"11"
Existing Redis recipient-portal session id; when omitted a new one is generated.
Example:
"a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2"