> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quiva.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Email a client a sign-in link

> Root and administrators. Emails one client of the caller's account a single-use sign-in link inside a published email template, so a flow can send a branded email the client opens in one click. The template must carry the `{sign_in_url}` tag. The link is a credential: it is never returned and never logged. 4xx when the client or template is missing or the template has unresolved tags.



## OpenAPI

````yaml /api-reference/endpoint/accounts/openapi.json post /accounts/send-client-sign-in
openapi: 3.0.3
info:
  title: quiva.ai Accounts API
  description: >-
    API for managing accounts, users, authentication, and payments in the
    quiva.ai platform
  version: 1.0.0
  contact:
    name: quiva.ai Support
    url: https://app.quiva.ai
servers:
  - url: https://api.quiva.ai
    description: Production API server
security:
  - bearerAuth: []
  - apiKeyAuth: []
tags:
  - name: Account Management
    description: Operations related to account creation, updating, and deletion
  - name: User Management
    description: Operations related to user creation, updating, and deletion
  - name: Authentication
    description: Operations related to authentication and session management
  - name: API Keys
    description: Operations related to API key management
  - name: Multi-Factor Authentication
    description: Operations related to MFA setup and verification
  - name: Payment
    description: Operations related to subscription and payment management
  - name: Mesh Nodes
    description: Operations related to mesh node management
  - name: Integrations
    description: Machine identities and client credentials for task sync
  - name: Task Subscriptions
    description: Webhook subscriptions that push task events to your endpoint
  - name: Email Templates
    description: Account email templates used by flows, Abbie and the client sign-in email
  - name: Branding
    description: Sign-in branding and account images
  - name: Client Access
    description: Passwordless sign-in and invitations for client users
  - name: Sync Packages
    description: Install, upgrade and remove sync packages for an account
  - name: Terms
    description: Terms documents, provider terms and the acceptance log
  - name: Email Sending
    description: Sending identity and outbound email
  - name: Usage and Billing
    description: Cost events, billing events, credit budget and spend guard
  - name: Notifications
    description: In-app notifications for the signed-in user
  - name: Resource Access
    description: Per-user grants on resources such as spaces
  - name: Document Branding
    description: Account theme and logo used on generated documents
paths:
  /accounts/send-client-sign-in:
    post:
      tags:
        - Authentication
      summary: Email a client a sign-in link
      description: >-
        Root and administrators. Emails one client of the caller's account a
        single-use sign-in link inside a published email template, so a flow can
        send a branded email the client opens in one click. The template must
        carry the `{sign_in_url}` tag. The link is a credential: it is never
        returned and never logged. 4xx when the client or template is missing or
        the template has unresolved tags.
      operationId: sendClientSignIn
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SendClientSignInRequest'
            example:
              email: client@example.com
              template_key: client-sign-in
              data:
                first_name: Sam
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SuccessResponse'
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    SendClientSignInRequest:
      type: object
      required:
        - email
        - template_key
      properties:
        email:
          type: string
          format: email
          description: >-
            The client. The mail goes to the address on file for that client,
            never to an address in the body.
        template_key:
          type: string
          description: >-
            Key of a published email template that carries the `{sign_in_url}`
            tag
        data:
          type: object
          additionalProperties: true
          description: >-
            Values for the template's tags. `sign_in_url` is always the minted
            link.
        redirect_path:
          type: string
          description: Path in the app the client lands on after signing in
        contact_folder:
          type: string
          description: Folder the mail belongs to, echoed in delivery events
        task_id:
          type: string
          description: Task the mail belongs to, echoed in delivery events
    SuccessResponse:
      type: object
      properties:
        message:
          type: string
    Error:
      type: object
      properties:
        error:
          type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    apiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.