Developer docs menu

Reference

Acceptable use

The rules for software that calls the API: act for a real customer, say who you are, and take only what you need.

These rules apply to anything that calls the API or the MCP server, with a key or without one. They sit alongside the Terms of Service.

Act for a real customer

  • Ask for a booking only when a person has asked you to make it, and give that person’s own email address. They get the email and they decide.

  • Hold a time only when you mean to book it. Let go of a hold you no longer need with DELETE /businesses/{slug}/holds/{token}.

  • Practice in the sandbox, never on a real business.

Say who you are

  • Send X-Agent with your agent’s real name on every request. Do not use another product’s name.

  • Tell the customer the business’s name, price and time as the API gave them. Do not change a price or promise a time you do not hold.

Take only what you need

  • Keep to the rate limits. On a 429, wait for Retry-After before trying again.

  • Read a business to serve a customer’s request. Do not copy businesses, prices or free times in bulk to build a directory or a data set.

  • When a business answers agents_off_for_business, send the customer to its booking page and leave it there.

Keys and records

  • An API key is a password. Keep it on your server, never in a web page, an app or a prompt.

  • What a key reads belongs to the business: its customers, bookings and quotes. Use it only for that business’s own work.

  • Webhook endpoints must be yours to receive on.

What happens otherwise

A caller that breaks these rules can be slowed or blocked, and a key can be revoked, without notice. To report a problem or ask about a use that is not covered here, get in touch.