# Plans and API Access

Most Bento REST endpoints are available to every account with API keys for the site. A few endpoints are gated because they can be expensive, reveal broad account data, or need account-specific review before use.


> Use this page as the central reference for API limits. Endpoint pages still win when they document a more specific limit.


## Default API Limits {{ id: 'default-api-limits' }}

These defaults apply unless an endpoint page says otherwise.

| Endpoint family | Default limit |
| --- | --- |
| `/api/v1/fetch/*` | 100 requests per minute |
| `/api/v1/batch/*` | 100 requests per minute |
| `/api/v1/experimental/*` | 100 requests per minute |
| `/api/v1/stats/*` | 60 requests per hour |

When you receive a `429`, slow down and retry with exponential backoff. Batch endpoints are designed for bulk work, so prefer one request with many records over many single-record requests.

## Endpoint Access By Plan {{ id: 'endpoint-access-by-plan' }}


  - **/batch/events** (`All API-enabled accounts`): 
    Track user activity, update fields, create people, and trigger workflows.
  
  - **/batch/subscribers** (`All API-enabled accounts`): 
    Import or update subscribers without triggering automations.
  
  - **/batch/emails** (`All API-enabled accounts`): 
    Queue transactional or one-off emails at the documented send pace.
  
  - **/fetch/search** (`Enterprise`): 
    Search subscribers by filters. Contact support if you need access.
  
  - **/stats/*** (`All API-enabled accounts`): 
    Read stats for backend dashboards and internal reporting.
  


> ⚠️ **Warning**
> Do not work around an access gate by scraping dashboard pages or polling broad list endpoints. Contact support so we can recommend the right endpoint or export path.


## Transactional Email Limits {{ id: 'transactional-email-limits' }}

The [Emails API](/docs/emails_api) accepts up to 60 email objects per request and sends at a default pace of 60 emails per minute.

Messages that look risky can be slowed down further. Examples include emails with URL shorteners, emoji-heavy content, or user-controlled personalization in sensitive flows. If you send password resets, invites, login links, or receipts, also rate limit the user-facing action in your own app.

## When To Contact Support {{ id: 'when-to-contact-support' }}

Contact `support@bentonow.com` when you need:

- higher transactional email send pace
- Enterprise subscriber search access
- a data export path that is not covered by the public API
- guidance on bulk imports, migrations, or account-specific rate limits

## Related docs

- [API conventions](/docs/api/conventions)
- [Developer API overview](/docs/developer_guides/introduction)
- [Subscribers API](/docs/subscribers)
- [Emails API](/docs/emails_api)