> ## Documentation Index > Fetch the complete documentation index at: https://api-docs.helpyousponsor.com/llms.txt > Use this file to discover all available pages before exploring further. # Request a recipient-portal verification code by email > First step of the recipient-portal login flow. Looks up the recipient by tenant-scoped email, issues a six-digit numeric code and magic link for 15 minutes, and invalidates the previous code for that client/program/recipient/email scope. Shared emails return `status=selection_required` so the caller can re-submit with `entity_id`. ## OpenAPI ````yaml post /frontend/recipient-portal/login/{client_id}/{program_id}/{session_id} openapi: 3.0.0 info: title: Gratona API description: >- REST API for the Gratona fundraising platform, including donor, donation, sponsorship, program, event, and integration workflows. Endpoints are organized by tag. Most endpoints require either a Passport bearer token or an issued API key — see the Security Schemes section. contact: name: Gratona Engineering url: https://gratona.com email: devs@gratona.com version: 1.0.0 servers: - url: https://api.gratona.com/v1 description: Server Version 1.0.0 security: [] tags: - name: Auth description: >- Login, signup, logout, password reset, and email verification for admin users and donors. - name: Donors description: >- Donor records: CRUD, profile fields, household linkage, search, filters, merge, and duplicate detection. - name: Donations description: >- Individual donation records, recurring commitments, soft credits, refunds, designations, and exports. - name: Sponsorships description: >- Donor-to-entity sponsorship relationships, lifecycle transitions, and sponsorship-specific filters. - name: Entities description: >- Recipient records (children, families, projects, animals, etc.), their status, and entity-level fields. - name: Programs description: >- Program / campaign configuration: hierarchy, settings, and program-level metadata. - name: Forms description: >- Custom form builder (HysForm), form fields, standardized donor fields, and field migrations. - name: Trips description: >- Mission-trip management: trips, participants, budgets, tasks, e-signatures, fundraising milestones, and background checks. - name: Communications description: >- Email templates, SMS, newsletters, donor email manager, and per-donor notes. - name: Payments description: >- Payment-gateway management (Stripe, PayPal, Flutterwave, QuickBooks). Excludes inbound webhooks — see the Webhooks tag. - name: Reports description: Dashboards, analytics, scheduled reports, and exports. - name: Admin description: >- Client-account administration: users, groups/permissions, settings, integrations, and account lifecycle. - name: Donor Portal description: >- Endpoints consumed by the donor-facing portal (donor login, dashboard, donation history, messages). - name: Recipient Portal description: Endpoints consumed by the recipient-facing portal. - name: Public description: >- Unauthenticated public endpoints: donor signup, public trip pages, peer-to-peer campaigns, public checkout. - name: Webhooks description: >- Inbound webhooks from third parties (Stripe, PayPal, Flutterwave, Checkr, DropboxSign). Annotated minimally for reference; payload shapes are owned by the upstream provider. - name: Client description: Client - name: Email Settings description: Email Settings - name: Admin Dashboard description: Admin Dashboard - name: Historical Archived Updates description: Historical Archived Updates - name: Team & access description: Team & access - name: Files description: Files - name: Wrapped description: Wrapped - name: Donor SignUp description: Donor SignUp - name: Frontend description: Frontend - name: User description: User paths: /frontend/recipient-portal/login/{client_id}/{program_id}/{session_id}: post: tags: - Recipient Portal summary: Request a recipient-portal verification code by email description: >- First step of the recipient-portal login flow. Looks up the recipient by tenant-scoped email, issues a six-digit numeric code and magic link for 15 minutes, and invalidates the previous code for that client/program/recipient/email scope. Shared emails return `status=selection_required` so the caller can re-submit with `entity_id`. operationId: 4a86ac8ccef983f1957a733bfe08cacc parameters: - name: client_id in: path required: true schema: type: integer format: int64 example: 207 - name: program_id in: path required: true schema: type: string example: '11' - name: session_id in: path required: true schema: type: string requestBody: required: true content: application/json: schema: required: - email properties: email: description: 'Recipient email. Validator rule: `required|email`.' type: string format: email example: recipient@example.com entity_id: description: >- Required only on the second submission when the email matched multiple entities. Validator rule: `nullable|integer`. type: integer format: int64 example: null nullable: true type: object responses: '200': description: >- Either the verification code was emailed (`status=success`) or the email matched multiple recipients and the caller must pick one (`status=selection_required` with `entities` array). content: application/json: schema: properties: status: type: string enum: - success - selection_required message: type: string entities: type: array items: properties: id: type: integer example: 4711 name: type: string example: Jane Doe type: object type: object '400': description: Invalid entity selection. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '422': description: Validation failed. content: application/json: schema: $ref: '#/components/schemas/ValidationErrorResponse' '429': description: The tenant/endpoint passwordless budget was exceeded. content: application/json: schema: properties: status: type: string example: error message: type: string example: Too many sign-in attempts. Please wait and try again. type: object security: [] components: schemas: ErrorResponse: title: ErrorResponse description: >- Generic error envelope used by most controllers. Most error responses pair a human-readable `message` with `status: error`. Some endpoints additionally include `errors` (validator errors), `error` (legacy single-error string), `code`, or domain-specific context fields. required: - message properties: message: description: Human-readable error message. type: string example: Something went wrong. Please try again. status: description: >- Always the literal string `error` for failures. Some endpoints omit this field. type: string example: error error: description: Legacy single error code/string used by older endpoints. type: string example: invalid_request nullable: true code: description: >- Optional application-level error code (not all endpoints populate this). type: string example: DONOR_NOT_FOUND nullable: true type: object ValidationErrorResponse: title: ValidationErrorResponse description: >- Returned with HTTP 422 when `Validator::make($data, $rules)` fails. The `errors` map is keyed by the failing field name; each value is an array of human-readable error messages for that field. Most controllers also include a top-level `status: error`. required: - errors properties: errors: description: >- Map of field name to array of validator error messages. Example: `{email: [The email field is required.], amount: [The amount must be a number.]}`. type: object additionalProperties: type: array items: type: string status: description: Always the literal string `error`. type: string example: error message: description: >- Optional summary message — present on some endpoints, absent on others. type: string example: The given data was invalid. nullable: true type: object ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.