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

# List configured email providers

> Reports which email providers the relay is *capable* of authorizing against — that is, which provider OAuth client IDs and secrets are configured on the backend. Frontends use this to show or hide "Connect Gmail" / "Connect Outlook" buttons. Always returns 200 even when no providers are configured.



## OpenAPI

````yaml /api-reference/openapi.yaml get /api/email/accounts/providers/available
openapi: 3.0.3
info:
  title: Tether Relay and Tether API
  version: 1.0.0
  description: >-
    Route-derived OpenAPI contract generated from tether-relay backend sources.
    Regenerate with scripts/sync-openapi-from-backend.mjs.
servers:
  - url: https://your-instance.example.com
    description: Production
  - url: http://localhost:2212
    description: Local API service
security: []
tags:
  - name: AI
  - name: Applications
  - name: Approval
  - name: Auth
  - name: Automations
  - name: Calls
  - name: Campaigns
  - name: Contact Analytics
  - name: Contact Metrics
  - name: Contact Notes
  - name: Contacts
  - name: Conversation Monitor
  - name: Conversations
  - name: Departments
  - name: Email
  - name: Escalation Dashboard
  - name: Event Logs
  - name: Google Sheets
  - name: Marketplace
  - name: Messages
  - name: Notification Sounds
  - name: Notifications
  - name: Org Snapshots
  - name: Organizations
  - name: Outreach
  - name: Outreach Metrics
  - name: Outreach Sources
  - name: Pipelines
  - name: Processes
  - name: Prompts
  - name: Reminders
  - name: Sms
  - name: Templates
  - name: Traces
  - name: Training
  - name: Upload
  - name: User Snapshots
  - name: Users
  - name: Vertical
  - name: Webchats
  - name: Webhook
paths:
  /api/email/accounts/providers/available:
    get:
      tags:
        - Email
      summary: List configured email providers
      description: >-
        Reports which email providers the relay is *capable* of authorizing
        against — that is, which provider OAuth client IDs and secrets are
        configured on the backend. Frontends use this to show or hide "Connect
        Gmail" / "Connect Outlook" buttons. Always returns 200 even when no
        providers are configured.
      operationId: get_email_accounts_providers_available
      responses:
        '200':
          description: >-
            Provider availability map keyed by provider name. `true` means OAuth
            credentials are configured on this backend.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/EmailProviderAvailabilityResponse'
      security:
        - bearerAuth: []
components:
  schemas:
    EmailProviderAvailabilityResponse:
      type: object
      description: >-
        Boolean map indicating which email providers have OAuth credentials
        configured on this backend. Absent or `false` means the provider cannot
        be used for new connections (the relay was deployed without that
        provider's client id/secret).
      properties:
        gmail:
          type: boolean
          description: Gmail OAuth is configured.
        outlook:
          type: boolean
          description: Outlook OAuth is configured.
      required:
        - gmail
        - outlook
      additionalProperties: true
      example:
        gmail: true
        outlook: false
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````