Dates and times. Use RFC 3339 with an offset for every date and time you send: Z for UTC, or a numeric offset such as +08:00. Responses are not always in UTC: bookings are returned in UTC, and available slots in the offset of the timezone you request. Read the offset in each value instead of assuming UTC; see Time standards in the Getting Started section above.
Updating by id. When you update a booking, an event, or a service, an id in the request body must match the id in the URL, otherwise you receive 400. You can also leave the id out of the body.
Rate limits. The v2 API is rate limited. If you exceed the limit you receive 429 Too Many Requests.
Full details. Every endpoint, field, limit, and example is in the endpoint sections of this page.