Quickstart: your first recorded meeting

This runs the whole flow with your account key: you play both your backend and your user.

1. Create a workspace

Use the account key (sk_live_…) _æfer gave you when your account opened. Send it bare in Authorization, as every example here does (see Authentication). A new account has no workspaces yet, so create one for this test, as you will for each customer:

export AEFER_API_KEY='sk_live_your_account_key'

curl -X POST "https://api.aefer.ai/api/v1/workspaces" \
  -H "Authorization: $AEFER_API_KEY" \
  -H "Aefer-Version: 2026-11-13" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Quickstart test", "client_reference_id": "quickstart-test" }'

Keep its id. client_reference_id is your own id for the customer, unique in your account: sending the same one again answers 422 taken instead of making a second workspace.

export WORKSPACE_ID=wks_01k6a2r9s8x7c2dvq3m5n6p4ab

2. Register a webhook endpoint

Optional here: you can skip it and read the meeting instead in step 6. To receive webhooks on your machine, see Test locally.

curl -X POST "https://api.aefer.ai/api/v1/webhook_endpoints" \
  -H "Authorization: $AEFER_API_KEY" \
  -H "Aefer-Version: 2026-11-13" \
  -H "Content-Type: application/json" \
  -d '{
    "workspace_id": "'"$WORKSPACE_ID"'",
    "url": "https://your-tunnel.example.com/webhooks",
    "enabled_events": ["calendar_connection.connected", "meeting.created", "meeting.updated", "meeting.finished"]
  }'

3. Connect your calendar

A workspace your account key creates starts with no members. Add yourself as one, with the email of the calendar you want to test:

curl -X POST "https://api.aefer.ai/api/v1/members" \
  -H "Authorization: $AEFER_API_KEY" \
  -H "Aefer-Version: 2026-11-13" \
  -H "Content-Type: application/json" \
  -d '{
    "workspace_id": "'"$WORKSPACE_ID"'",
    "email": "you@example.com",
    "name": "Your Name"
  }'

Use your real address: example.com and disposable domains are refused (422 invalid). Nothing is emailed to that address. Keep the member’s id:

export MEMBER_ID=mem_01k69x9s8x7c2dvq3m5n6p4ab

Create a connect link for yourself as your backend would, then open its url in your browser:

curl -X POST "https://api.aefer.ai/api/v1/calendar_connect_links" \
  -H "Authorization: $AEFER_API_KEY" \
  -H "Aefer-Version: 2026-11-13" \
  -H "Content-Type: application/json" \
  -d '{
    "workspace_id": "'"$WORKSPACE_ID"'",
    "member_id": "'"$MEMBER_ID"'",
    "provider": "google",
    "return_url": "https://example.com/connected"
  }'

Approve access with the Google account whose calendar you want to test. Your users will go through the same link with member_data instead of member_id: see Connect calendars. A link without member_id never connects a workspace owner or admin.

4. See your meetings

Give the calendar a minute to sync, then:

curl -G "https://api.aefer.ai/api/v1/meetings" \
  -H "Authorization: $AEFER_API_KEY" \
  -H "Aefer-Version: 2026-11-13" \
  -d workspace_id=$WORKSPACE_ID \
  -d member_id=$MEMBER_ID \
  -d phase=upcoming \
  -d include=settings

Each meeting says whether the notetaker will join, in settings.recording.enabled.

5. Record a call

Open meet.new, then send the notetaker to it:

curl -X POST "https://api.aefer.ai/api/v1/bots" \
  -H "Authorization: $AEFER_API_KEY" \
  -H "Aefer-Version: 2026-11-13" \
  -H "Content-Type: application/json" \
  -d '{
    "workspace_id": "'"$WORKSPACE_ID"'",
    "member_id": "'"$MEMBER_ID"'",
    "meeting_url": "https://meet.google.com/abc-defg-hij"
  }'

Keep the meeting_id from the response. Admit the notetaker when it asks to join, talk for a minute or two, then leave the call.

export MEETING_ID=mtg_01k6b1r9s8x7c2dvq3m5n6p4ab

6. Read the results

Your endpoint receives meeting.finished a few minutes after the call. Without one, read the meeting every 30 seconds or so until results.status is ready or failed:

curl "https://api.aefer.ai/api/v1/meetings/$MEETING_ID" \
  -H "Authorization: $AEFER_API_KEY" \
  -H "Aefer-Version: 2026-11-13"

Then:

curl "https://api.aefer.ai/api/v1/meetings/$MEETING_ID/results" \
  -H "Authorization: $AEFER_API_KEY" \
  -H "Aefer-Version: 2026-11-13"

You get the transcript as speaker turns, the speakers, the summary with its action items, and the audio. A finished meeting explains every field.

Build the screens: start with Connect calendar.

Get started

Getting meetings in

Build the screens