REST API

​

OpenAPI specification

​

Authentication

curl --request GET \
  --url https://api.daily.co/v1/rooms \
  --header "Authorization: Bearer DAILY_API_KEY"

​

Rate limits

• For most of our API endpoints, including POST /rooms, DELETE /rooms/:name, GET /rooms, presence, and webhooks, you can expect a limit of 99 requests over a 5 second window.
• For analytics and data endpoints, including GET /meetings, GET /recordings, usage, API and webhook logs, transcripts, the batch processor, phone numbers, verified caller IDs, SIP trunks, and domain dial-in config, you can expect 49 requests over a 30 second window.
• For starting a dial-out, starting a dial-in, and starting a live stream, you can expect 4 requests over a 5 second window. These three share one budget: a dial-out start and a live stream start with the same API key both count against the same window.
• For starting a recording, you can expect 4 requests over a 5 second window. Starting a recording has its own separate budget, so it does not use up any of the budget shared by dial-out, dial-in, and live streaming. That means you can start a recording and start a dial-out at the same moment without one crowding out the other.
• For batch room create and batch room delete, you can expect 9 requests over a 30 second window. Each of these requests can include up to 1000 rooms, and creates still count toward your account’s room limit.
• POST /meeting-tokens does not currently have a per-endpoint rate limit. If you need to issue a large number of tokens at once, consider self-signing tokens instead of calling the API for each one.

​

Errors

{
  "error": "invalid-request-error",
  "info": "bad Authorization header format"
}

​

HTTP status codes

​

Error types

​

Pagination

​

Fetching 100 results at a time

• The limit argument sets the size of the page (how many objects each page contains), and defaults to a value of 100.
• The starting_after argument sets the starting point of the page and is used to fetch “subsequent” pages of results — as if you were paging through a book from front to back.
• The ending_before argument is the opposite, and is used to fetch previous pages of results — as if you were paging through a book from back to front.
• A special ending_before argument, OLDEST, is available to facilitate fetching pages of results “backwards,” from oldest objects to newest.

​

Examples

# List your five most recently created rooms
curl -H "Content-Type: application/json" \
     -H "Authorization: Bearer DAILY_API_KEY" \
     https://api.daily.co/v1/rooms?limit=5

# List your five oldest rooms
curl -H "Content-Type: application/json" \
     -H "Authorization: Bearer DAILY_API_KEY" \
     https://api.daily.co/v1/rooms?limit=5&ending_before=OLDEST

​

Pseudocode for fetching all results

// Get first page of results
let rooms = getPageOfRooms({
  endpoint: 'https://api.daily.co/v1/rooms',
});

while (rooms.data.length > 0) {
  for (var i = 0; i < rooms.data.length; i++) {
    doSomeStuff(rooms.data[i]);
  }

  // Fetch next page
  rooms = getPageOfRooms({
    endpoint:
      'https://api.daily.co/v1/rooms?starting_after=' +
      rooms.data[rooms.data.length - 1].id,
  });
}