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

# Get sender logo



## OpenAPI

````yaml /openapi/escrybe.en.yaml get /api/v2/logo
openapi: 3.1.0
info:
  title: Escrybe API
  version: 1.0.0
  description: >
    REST API for the Escrybe platform — send physical letters, registered
    letters, telegrams and e-Carta through Brazilian Correios, dispatch legally
    registered e-mails, and send WhatsApp messages with certified timestamps.


    ## Authentication

    Every account has a personal **`securityToken`** (find it in the panel under
    *Account → API*). Three products use it differently:


    | Product | Scheme | How | |---------|--------|-----| | Letters / Telegram /
    e-Carta, Registered E-mail, Receipts | API token | Send `userSecurityToken`
    as a query/body parameter, or `securityToken` as a header | | WhatsApp |
    HTTP Basic | `Authorization: Basic base64(email:securityToken)` |


    > The letter and e-mail **read** routes (`get`, `balance`, `download`, >
    `delete`) take the token as the first URL **path** segment — e.g. >
    `/api/v2/get/{securityToken}/{job_id}`.


    ## Response envelopes

    Most endpoints reply with the standard envelope `{"status": <http code>,
    "status_message": "...", "data": ...}` — this covers Letters/Telegram,
    Registered E-mail, and the WhatsApp message and sender endpoints. The
    WhatsApp **template** endpoints (and template sync) use `{"code": <http
    code>, "status": "success|error", "message": "...", "data": ...,
    "request_id": "..."}`; the logo endpoint uses the same shape without
    `request_id`. See the schema of each endpoint.


    A request that is accepted returns an HTTP `200` with a success payload;
    validation problems return `400`, bad credentials `401`, and forbidden
    access `403`. Unsupported HTTP methods return `405`, repeated failed
    authentication attempts return `429`, and the letter and e-mail endpoints
    return `503` during maintenance windows.
  contact:
    name: Escrybe Support
    url: https://escrybe.com.br
servers:
  - url: https://app.escrybe.com.br
    description: Production
  - url: https://homolog.escrybe.com.br
    description: Staging
security:
  - securityTokenQuery: []
tags:
  - name: Letters & Telegram
    description: Create and manage letter, telegram and e-Carta orders (Correios).
  - name: Account & Favorites
    description: Account balance, saved contacts and sender logo.
  - name: Registered E-mail
    description: Send and track legally registered e-mails.
  - name: WhatsApp Messages
    description: Send WhatsApp messages and download certified-timestamp attestations.
  - name: WhatsApp Senders
    description: Manage WhatsApp Business numbers (senders).
  - name: WhatsApp Templates
    description: Create, sync and manage WhatsApp message templates.
  - name: Receipts
    description: Download legal receipts for any order.
paths:
  /api/v2/logo:
    get:
      tags:
        - Account & Favorites
      summary: Get sender logo
      operationId: getLogo
      responses:
        '200':
          description: Logo URL
          content:
            application/json:
              schema:
                allOf:
                  - $ref: '#/components/schemas/LogoEnvelope'
                  - properties:
                      data:
                        type: object
                        properties:
                          logo_url:
                            type: string
                            nullable: true
        '401':
          $ref: '#/components/responses/LogoUnauthorized'
      security:
        - securityTokenHeader: []
        - bearerAuth: []
        - securityTokenQuery: []
components:
  schemas:
    LogoEnvelope:
      type: object
      description: Envelope used by the sender-logo endpoint.
      properties:
        code:
          type: integer
          example: 200
        status:
          type: string
          example: success
        message:
          type: string
          nullable: true
        data: {}
  responses:
    LogoUnauthorized:
      description: Invalid token
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/LogoEnvelope'
          example:
            code: 401
            status: error
            message: Token de segurança inválido
            data: null
  securitySchemes:
    securityTokenQuery:
      type: apiKey
      in: query
      name: userSecurityToken
      description: >-
        Your account security token, sent as the `userSecurityToken` query or
        form parameter.
    securityTokenHeader:
      type: apiKey
      in: header
      name: securityToken
      description: Your account security token, sent in the `securityToken` header.
    bearerAuth:
      type: http
      scheme: bearer
      description: 'Your account security token sent as `Authorization: Bearer <token>`.'

````