Each API key may make 100 requests a minute, counted per key, in fixed one-minute windows. MCP tool calls count against the key they use, exactly like REST requests. Past the limit, requests answer 429 with a Retry-After header giving the seconds to wait.
HTTP/1.1 429 Too Many Requests
Retry-After: 42
Content-Type: application/json
{
"error": {
"code": "RATE_LIMITED",
"message": "Too many requests. Each key may make 100 requests a minute."
}
}Staying under the limit
- Use webhooks to learn about payments instead of polling the list endpoints.
- Page with the largest
limityou need (up to 100) and filter on the server. - Give each integration its own key: each key has its own limit, and you can revoke one without the others.
- On
429, waitRetry-Afterseconds before retrying; don't retry in a tight loop.
Other limits
| Limit | Answer |
|---|---|
| An invoice can be emailed at most once every 24 hours (Send invoice) | 429 TOO_SOON with Retry-After |
| A payment link's price is $1.00 to $10,000.00 | 400 INVALID_INPUT |
| An invoice totals $1.00 to $100,000.00 | 400 INVALID_INPUT |