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

# Resolved scope for the current token



## OpenAPI

````yaml /api-reference/openapi-public.json get /auth/me
openapi: 3.0.3
info:
  description: >-
    The API your own systems use: place and follow calls, have an AI agent call
    someone, run campaigns and get their results, keep contacts in step with
    your CRM, and receive signed webhooks. Authenticate with an integration key
    (Authorization: Bearer ft_...), used only from the IP addresses it allows.
  title: FireTone API
  version: 0.1.0
servers:
  - description: Your platform's API host
    url: https://{host}/api/v1
    variables:
      host:
        default: api.firet.one
security:
  - bearerAuth: []
tags:
  - name: Auth
  - description: >-
      Live calls and what can be done to them: hang up, hold, transfer, park,
      merge, monitor, whisper; the Desk's own call.
    name: Calls
  - description: 'Outbound campaigns: contacts, attempts, outcomes.'
    name: Campaigns
  - description: 'Customers: who called, what is known about them, and their memory.'
    name: Contacts
  - description: What was said on an AI call, and the review of it.
    name: Conversations
  - description: >-
      Your own systems: HTTP connections an IVR calls mid-call, and webhooks for
      call events. Tenant URLs must be public https addresses.
    name: Integrations
  - name: Live
  - name: Provisioning
  - name: Reporting
  - description: Tickets raised by people, agents and the API.
    name: Tickets
  - description: Messages left for an extension or a queue.
    name: Voicemail
paths:
  /auth/me:
    get:
      tags:
        - Auth
      summary: Resolved scope for the current token
      operationId: getAuthMe
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Me'
          description: OK
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    Me:
      description: >-
        The RESOLVED scope, not merely the token's claims, so the panel can
        render navigation without guessing at permissions.
      properties:
        all_organisations:
          type: boolean
        organisation_ids:
          items:
            format: uuid
            type: string
          type: array
        team_ids:
          items:
            format: uuid
            type: string
          type: array
        user:
          $ref: '#/components/schemas/User'
      required:
        - user
        - all_organisations
        - organisation_ids
        - team_ids
      type: object
    User:
      properties:
        email:
          format: email
          type: string
        id:
          format: uuid
          type: string
        operator_id:
          format: uuid
          type: string
        organisation_id:
          format: uuid
          type: string
        role:
          enum:
            - operator_admin
            - org_admin
            - team_supervisor
            - agent
          type: string
        team_id:
          format: uuid
          type: string
      required:
        - id
        - email
        - role
      type: object
    Error:
      properties:
        error:
          properties:
            code:
              enum:
                - invalid_request
                - invalid_credentials
                - unauthenticated
                - forbidden
                - not_found
                - conflict
                - internal
              type: string
            message:
              type: string
          required:
            - code
            - message
          type: object
      required:
        - error
      type: object
  responses:
    Unauthorized:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
      description: Missing, invalid or expired token
  securitySchemes:
    bearerAuth:
      bearerFormat: JWT or API key
      description: >-
        Every request sends `Authorization: Bearer <token>`. The token is either
        a panel session (a JWT from /auth/login, 12 hours) or an API key
        `ft_<id>_<secret>`. An API key is accepted only from an address on its
        IP allowlist (403 ip_not_allowed otherwise; 403 ip_allowlist_required
        for an old key that has none), is limited to its rate per minute (429
        rate_limited with Retry-After; X-RateLimit-Limit/Remaining/Reset on
        every response), and at most 60 call placements a minute.
      scheme: bearer
      type: http

````