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

# Show one variant



## OpenAPI

````yaml /api-reference/openapi.json get /v1/signatures/{signature_id}/variants/{kind}
openapi: 3.0.1
info:
  title: Scribe Public API
  version: v1
  description: >-
    REST API to manage email signatures, teammates, smart fields, and marketing
    campaigns in your Scribe workspace. Every request uses JSON and is
    authenticated with a workspace API key. Endpoints are versioned under `/v1`,
    for example `https://api.scribe-mail.com/v1/signatures`.
  contact:
    name: Scribe Support
    url: https://help.scribe-mail.com/en
servers:
  - url: https://api.scribe-mail.com
    description: Production
security: []
tags:
  - name: Signatures
    description: >-
      Create, update, publish, and install email signature templates, and
      control which teammates each signature is assigned to.
  - name: Teammates
    description: >-
      Manage the people whose signatures Scribe deploys, and set their smart
      field values.
  - name: Emails
    description: >-
      Manage teammate email addresses, including the aliases that receive a
      signature.
  - name: Smart fields
    description: >-
      Define the dynamic fields, such as job title, phone number, or calendar
      link, that populate signatures.
  - name: Folders
    description: Organize signature templates into folders.
  - name: Assets
    description: >-
      Upload and manage the images and files used across signatures and
      campaigns.
  - name: Marketing campaigns
    description: >-
      Schedule, pause, and resume the promotional banners shown in your team's
      signatures.
  - name: Integrations
    description: >-
      List the directory, HRIS, and email integrations connected to your
      workspace.
  - name: Integration entities
    description: >-
      List the org units and groups from your connected integrations, used to
      target signatures.
  - name: Financial documents
    description: List the invoices and financial documents for your workspace.
paths:
  /v1/signatures/{signature_id}/variants/{kind}:
    parameters:
      - name: signature_id
        in: path
        required: true
        schema:
          type: string
      - name: kind
        in: path
        schema:
          type: string
          enum:
            - reply
            - internal
        required: true
    get:
      tags:
        - Signatures
      summary: Show one variant
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/signature_variant_response'
        '404':
          description: Unknown variant kind
      security:
        - ApiKey: []
components:
  schemas:
    signature_variant_response:
      type: object
      properties:
        data:
          $ref: '#/components/schemas/signature_variant'
      required:
        - data
      additionalProperties: false
    signature_variant:
      type: object
      properties:
        kind:
          type: string
          enum:
            - reply
            - internal
          description: >-
            Which variant: shown on reply emails (reply) or same-domain/internal
            emails (internal).
        exists:
          type: boolean
          description: >-
            Whether a distinct variant signature has been created. When false,
            replies/internal emails use the primary signature.
        id:
          type: string
          nullable: true
          description: >-
            UUID of the variant signature template (null when it does not exist
            yet).
        activated:
          type: boolean
          description: >-
            Whether the distinct variant is in effect (vs. falling back to the
            primary signature).
        hidden:
          type: boolean
          description: When true, no signature is shown on this kind of email at all.
        show_marketing_campaigns:
          type: boolean
          description: Whether marketing campaigns are appended to this kind of email.
        content:
          type: object
          nullable: true
          additionalProperties: true
          description: >-
            The variant's published block tree, returned verbatim. See
            signature_content for the write shape.
        draft_content:
          type: object
          nullable: true
          additionalProperties: true
          description: >-
            The variant's unpublished draft block tree, returned verbatim. See
            signature_content for the write shape.
        last_published_at:
          type: string
          format: date-time
          nullable: true
        created_at:
          type: string
          format: date-time
          nullable: true
        updated_at:
          type: string
          format: date-time
          nullable: true
      required:
        - kind
        - exists
        - id
        - activated
        - hidden
        - show_marketing_campaigns
        - content
        - draft_content
        - last_published_at
        - created_at
        - updated_at
      additionalProperties: false
  securitySchemes:
    ApiKey:
      type: http
      scheme: bearer

````