Table of contents:

• Authentication
• Rate Limits
• Errors
• Pagination
  • Response
• Endpoints
  • Meetings
    • LIST Meetings
    • GET Meeting
• Resources
  • Meeting
  • Participant
  • ParticipantSession
• Best Practices

All requests use your team's API token and return JSON.

Note: You can directly access a markdown version of these docs here - perfect for feeding to agents / LLMs.

Authentication

Pass your API token as a Bearer token in the Authorization header:

Authorization: Bearer al_live_...

You can generate an API token from your team's settings page.

Rate Limits

Each response includes rate-limit headers:

Currently, our Teams plan can make up to 10,000 requests/month before becoming rate-limited.

Errors

Errors return a JSON body with a type and message:

{
  "error": {
    "type": "authentication_error",
    "message": "Invalid or missing API token."
  }
}

Pagination

List endpoints use cursor-based pagination.

Pass limit (1 - 50, default 25) and starting_after (the id of the last item) to page through results:

GET /api/v1/meetings?limit=10&starting_after=mtg_abc123

Response

{
  "object": "list",
  "data": [{}, {}, {}],
  "has_more": true,
  "next_cursor": "mtg_xyz789"
}

When has_more is true, pass next_cursor as the starting_after param to fetch the next page. When has_more is false, next_cursor is null.

Endpoints

Meetings

LIST Meetings

GET /api/v1/meetings

Returns meetings for your organization, newest first.

Parameters:

Example request:

curl https://attendlist.com/api/v1/meetings \
  -H "Authorization: Bearer al_live_..." \
  -d status=ended \
  -d limit=10 \
  -G

Response:

{
  "object": "list",
  "has_more": false,
  "next_cursor": null,
  "data": [
    {
      "id": "mtg_abc123",
      "object": "meeting",
      "code": "abc-defg-hij",
      "title": "Weekly standup",
      "status": "ended",
      "started_at": "2026-07-01T09:00:00Z",
      "ended_at": "2026-07-01T09:30:00Z",
      "duration_seconds": 1800,
      "tags": ["engineering"],
      "created_at": "2026-07-01T09:00:00Z"
    }
  ]
}

GET Meeting

GET /api/v1/meetings/:id

Returns a single meeting with its participants and sessions.

Example request:

curl https://attendlist.com/api/v1/meetings/mtg_abc123 \
  -H "Authorization: Bearer al_live_..."

Response:

{
  "id": "mtg_abc123",
  "object": "meeting",
  "code": "abc-defg-hij",
  "title": "Weekly standup",
  "status": "ended",
  "started_at": "2026-07-01T09:00:00Z",
  "ended_at": "2026-07-01T09:30:00Z",
  "duration_seconds": 1800,
  "tags": ["engineering"],
  "created_at": "2026-07-01T09:00:00Z",
  "participants": [
    {
      "id": "pt_xyz789",
      "object": "participant",
      "display_name": "Jane Smith",
      "email": "[email protected]",
      "photo_url": "https://...",
      "created_at": "2026-07-01T09:00:00Z"
    }
  ],
  "participant_sessions": [
    {
      "id": "ps_def456",
      "object": "participant_session",
      "participant_id": "pt_xyz789",
      "meeting_id": "mtg_abc123",
      "joined_at": "2026-07-01T09:00:00Z",
      "left_at": "2026-07-01T09:30:00Z",
      "screenshare_session": false,
      "duration_seconds": 1800,
      "created_at": "2026-07-01T09:00:00Z"
    }
  ]
}

Resources

Meeting

A meeting which was tracked by AttendList to produce an attendance report.

The Get endpoint also includes participants and participant_sessions:

Participant

Participants (attendees) of a given Meeting.

ParticipantSession

An instance of a Participant joining a Meeting. A Participant can have multiple ParticipantSessions if they left and rejoined a Meeting multiple times.

Best Practices

• Cache responses locally.
  • Your API quota is limited, so avoid fetching the same data repeatedly. Store response data on your side after the first request, and only re-fetch when you need fresh results (e.g. for new meetings).
• Use starting_after to sync incrementally.
  • Track the id of the most recent meeting you've fetched and cached locally. On subsequent requests, pass it as starting_after to only retrieve meetings you haven't seen yet, rather than re-fetching your entire history each time (which can quickly burn your API quota).