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

# Get a meeting

> Fetch one meeting by its composite `source:id` key, as returned by the list endpoint.



## OpenAPI

````yaml /openapi.json get /meetings/{key}
openapi: 3.1.0
info:
  title: Leadey API
  version: 1.4.0
  description: >-
    The Leadey API gives you programmatic access to your workspace: leads,
    companies, contacts, campaigns, meetings, opportunities and calls, plus the
    reporting metrics behind the Cockpit.


    Every request is authenticated with an organization-scoped API key, and
    every response is JSON. Reads work with any key. Writes — creating leads,
    adding notes, logging calls, managing tasks — need a key with write access,
    and are attributed to the workspace member that key belongs to. See [Writing
    data](/guides/writing-data).
servers:
  - url: https://backend.leadey.ai/v1
    description: Production
  - url: http://localhost:3001/v1
    description: Local development
security:
  - bearerAuth: []
tags:
  - name: Account
    description: The organization behind the API key.
  - name: Leads
    description: People enrolled in your campaigns.
  - name: Notes
    description: >-
      Free-text notes on a lead. Notes appear in the lead's timeline and in the
      Cockpit.
  - name: Tasks
    description: Follow-ups and reminders, each assigned to a workspace member.
  - name: Campaigns
    description: Outreach sequences and their performance.
  - name: Companies
    description: Companies in your workspace.
  - name: Contacts
    description: The canonical person record behind your leads.
  - name: Meetings
    description: Bookings merged across Calendly, Leadey and connected calendars.
  - name: Opportunities
    description: Deals, their value, and the pipelines they sit in.
  - name: Pipelines
    description: Deal pipelines and the stages inside them.
  - name: Calls
    description: Dial history, recordings and transcripts.
  - name: Metrics
    description: >-
      Aggregated reporting — meetings booked, sit rate, dial activity and
      pipeline value.
  - name: Reference
    description: The vocabularies other endpoints return values from.
paths:
  /meetings/{key}:
    get:
      tags:
        - Meetings
      summary: Get a meeting
      description: >-
        Fetch one meeting by its composite `source:id` key, as returned by the
        list endpoint.
      operationId: getMeeting
      parameters:
        - name: key
          in: path
          required: true
          description: Composite key, e.g. `leadey:sm_123`.
          schema:
            type: string
      responses:
        '200':
          description: Success.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    $ref: '#/components/schemas/Meeting'
              example:
                data:
                  id: mtg_5Rj8vKwT
                  source: google
                  title: Head of Revenue Operations
                  startTime: '2026-08-20T14:00:00.000Z'
                  endTime: '2026-08-20T14:30:00.000Z'
                  joinUrl: https://meet.google.com/abc-defg-hij
                  location: Manchester, United Kingdom
                  organizerEmail: sam@yourcompany.com
                  responseStatus: accepted
                  disposition: attended
                  leadId: lead_8Kq2mXvR
                  leadName: Priya Raman
                  company: Northwind Logistics
                  campaignId: fnl_Q3OutboundUK
                  hostUserId: user_2pXn4Rk
                  bookedByUserId: user_2pXn4Rk
                  selfBooked: true
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
        '429':
          $ref: '#/components/responses/RateLimited'
components:
  schemas:
    Meeting:
      type: object
      properties:
        id:
          type: string
          description: >-
            Composite `source:id`, e.g. `leadey:sm_123`. Meetings come from
            several sources, so the source is part of the identity.
          example: leadey:sm_123
        source:
          type: string
          enum:
            - google
            - outlook
            - calendly
            - leadey
        title:
          type: string
        startTime:
          type:
            - string
            - 'null'
          format: date-time
        endTime:
          type:
            - string
            - 'null'
          format: date-time
        joinUrl:
          type:
            - string
            - 'null'
        location:
          type:
            - string
            - 'null'
        organizerEmail:
          type:
            - string
            - 'null'
        responseStatus:
          type:
            - string
            - 'null'
          enum:
            - accepted
            - declined
            - tentative
            - needsAction
            - null
          description: The lead's RSVP, where the source reports one.
        disposition:
          type:
            - string
            - 'null'
          enum:
            - attended
            - no_show
            - null
          description: >-
            A rep's manual attendance mark on a past meeting. Null means nobody
            has marked it — NOT that it was missed.
        leadId:
          type:
            - string
            - 'null'
        leadName:
          type:
            - string
            - 'null'
        company:
          type:
            - string
            - 'null'
        campaignId:
          type:
            - string
            - 'null'
        hostUserId:
          type:
            - string
            - 'null'
        bookedByUserId:
          type:
            - string
            - 'null'
        selfBooked:
          type:
            - boolean
            - 'null'
          description: True when the lead booked the slot themselves.
      required:
        - id
        - title
        - startTime
        - endTime
    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            message:
              type: string
              description: Human-readable error message.
            details:
              type:
                - object
                - array
                - string
                - 'null'
              description: Optional structured detail.
          required:
            - message
  responses:
    Unauthorized:
      description: The API key is missing, invalid, or revoked.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              message: Invalid or revoked API key.
              details: null
    NotFound:
      description: The resource does not exist or is not in your workspace.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              message: Lead not found
              details: null
    RateLimited:
      description: Too many requests. Retry after the period in the `Retry-After` header.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              message: Rate limit exceeded. Retry in 42s.
              details: null
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Your API key, created in the Leadey dashboard under Settings → API Keys.
        Send it as `Authorization: Bearer leadey_sk_live_…`.

````