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

# Exchange a Privy token for a session

> Verifies a Privy access token and issues a session. `sub` is the Privy user id.



## OpenAPI

````yaml /openapi.yaml post /auth/privy
openapi: 3.1.0
info:
  title: Confiroll payroll-api
  version: 1.0.0
  description: >
    The Confiroll BFF (backend-for-frontend) for confidential contractor payroll
    on Stellar **testnet**. It issues session JWTs (SEP-10 wallet or Privy
    email) and fee-bumps browser-signed confidential transfers (Fork B). It
    holds operational keys only, never a user's signing or viewing key.


    Every handled error returns `{ "error": string }`. Request bodies are
    limited to 256 KiB.
servers:
  - url: https://api.confiroll.com
    description: Live testnet deployment
security: []
tags:
  - name: Health
    description: Service health.
  - name: Auth
    description: Session issuance via SEP-10 (wallet) or Privy (email).
  - name: Transfers
    description: The core confidential-payout call (Fork B fee-bump).
  - name: Batch runs
    description: Run a confidential batch of payouts.
  - name: Withdrawals and disclosure
    description: >-
      Withdraw and auditor disclosure. These routes return 501; the operations
      run in the client tooling.
  - name: Session and role
    description: Resolves the signed-in user's role.
  - name: Contractors
    description: Contractor directory (public data only).
  - name: Batches
    description: SDP-aligned batch (disbursement) records.
  - name: Payouts
    description: SDP-aligned payout (payment) records.
  - name: Funding
    description: Faucet and CCTP vault state.
paths:
  /auth/privy:
    post:
      tags:
        - Auth
      summary: Exchange a Privy token for a session
      description: >-
        Verifies a Privy access token and issues a session. `sub` is the Privy
        user id.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                token:
                  type: string
                  description: A Privy access token.
              required:
                - token
      responses:
        '200':
          description: Session issued
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Session'
              example:
                session: eyJhbGciOi...
                kind: privy
                sub: did:privy:abc123
        '400':
          description: token required
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: token required
        '401':
          description: Invalid Privy token
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: invalid Privy token
components:
  schemas:
    Session:
      type: object
      properties:
        session:
          type: string
          description: 'Signed session JWT. Send it as `Authorization: Bearer <session>`.'
        kind:
          type: string
          enum:
            - stellar
            - privy
        sub:
          type: string
          description: >-
            The subject: a Stellar G-address (stellar) or a Privy user id
            (privy).
      required:
        - session
        - kind
        - sub
    Error:
      type: object
      description: Standard error shape for all handled errors.
      properties:
        error:
          type: string
          description: Human-readable message.
      required:
        - error

````