Skip to content
Go to app
Signpost for Astro Get the theme →

Pagination, errors and rate limits

The conventions every endpoint shares, so your integration handles large lists and failures correctly.

Intermediate · 7 min read · Updated Sep 22, 2026

Every Meetlane endpoint follows the same rules for lists, errors and limits. Learn them once and they apply everywhere.

List endpoints return up to limit objects (default 20, maximum 100) and a has_more flag. To get the next page, pass the ID of the last object as starting_after:

Terminal window
curl "https://api.example.com/v1/bookings?limit=100&starting_after=bkg_8Kd2LmQ4" \
-H "Authorization: Bearer $MEETLANE_API_KEY"

The SDKs can iterate through every page for you:

for await (const booking of meetlane.bookings.list({ status: "confirmed" })) {
console.log(booking.id)
}

Meetlane uses standard HTTP status codes and returns a JSON body that explains the problem:

{
"error": {
"type": "invalid_request",
"code": "slot_unavailable",
"message": "The requested start time is no longer available.",
"param": "start"
}
}
Status Meaning
400 The request is missing a parameter or has an invalid value
401 The API key is missing or wrong
404 The object doesn’t exist, or belongs to the other mode
409 The slot was taken between your availability check and the booking
429 Too many requests
5xx Something went wrong on our side; retry with backoff

Each API key can make 100 requests per minute. When you exceed the limit, the API returns 429 with a Retry-After header in seconds.

Send an Idempotency-Key header with any POST request. If the network fails and you retry with the same key within 24 hours, Meetlane returns the original response instead of creating a second booking.