Skip to main content
PATCH
Update default limits
This endpoint changes how your platform treats users who do not have a subscription plan: whether they can use your platform, the price per minute they pay, and their default limits. Send only the keys you want to change: everything you leave out stays as it is. The response returns all the values after the change, in the same format as Get default limits.
This endpoint is available to the account owner (with an active plan) and to team members with Billing Access. Other users receive a 403 Forbidden error and nothing is saved.

Request Body

boolean
true lets users use your platform without a subscription plan
number
The price per minute for users without a subscription plan, in your currency. Up to 2 decimals, and at least minimum_minute_cost from Get default limits, which is your own cost per minute rounded up to the cent. A new price can take up to 15 minutes to apply to every user.
object
The default limits to change, keyed as in Limits. Limits you leave out stay unchanged. Count limits take an integer from -1 to 100000 (-1 means unlimited, 0 means none). Boolean limits take true or false.Limits can only be changed while allow_free_accounts is on, either already or in the same request. Otherwise the request returns 422 and nothing is saved.

Response

string
Success message
object
All your free account settings and default limits after the change, in the same format as Get default limits

How default limits work

  • Default limits apply to your users who do not have a subscription plan, and only while allow_free_accounts is on. Users with a plan get the limits of their plan.
  • Limits you set for a single user with Update user settings take priority over both.
  • Turning allow_free_accounts off keeps the default limits you set. They apply again when you turn it back on.

Limits

All of these except calendar_integrations can also be set for a single user with Update user settings.

Partial updates

  • Keys you leave out stay unchanged, and so do the limits you leave out of limits.
  • An unknown top-level field returns 422 with “The X field is not supported.”, and an unknown key inside limits returns 422 with “The limits field must be an object with only the supported keys.”. In both cases nothing is saved, not even the valid parts of the request.
  • Send only the keys you want to change.

Rate limit

The platform settings, default limits, user settings and plan endpoints share a limit of 60 requests per minute for each account. Above it they return 429, and the Retry-After response header tells you how many seconds to wait.

Example