Skip to main content

Rate limits and whitelisted IP addresses

Why CamBuildr sometimes refuses requests from one IP address, what visitors and integrations see, and how to whitelist an IP address or open a time-limited period for events.

Written by Domonkos Horváth

To protect your forms, votes and API from bots and abuse, CamBuildr limits how many requests can come from one IP address in a short time. Usually nobody notices. It matters when many real people share one internet connection, for example at an event on the venue's WiFi, or when your own server sends a lot of API requests.

How the limit works

  • CamBuildr counts requests per public IP address, per address (for example one particular form) and per method (sending vs. reading).

  • By default, 100 requests in 10 minutes are allowed. A few actions have a tighter limit (see the table below).

  • Opening a landing page is not limited. Only what the page sends back to CamBuildr counts, such as a form submission.

  • Once the limit is reached, further requests are refused until the 10 minutes are up. Then it starts again automatically.

What

Limit per IP address

Form submissions, survey answers, donations, API requests (default)

100 in 10 minutes

Votes on user posts and comments, landing page conversions, SMS verification

20 in 10 minutes

Saving an email tracking preference

30 in 10 minutes

Cookie consent records

1,000 in 10 minutes

Example: 150 people at an event sign up through the same form on the venue WiFi within a few minutes. To CamBuildr they all have the same public IP address. The first 100 submissions go through; the rest are refused until the 10 minutes are over.

What visitors and integrations see

  • Visitors on a landing page see the form's error message: "An error has occurred. Please try again later!" (German: "Ein Fehler ist aufgetreten. Bitte versuchen Sie es später noch einmal!"). Their entry is not saved.

  • API integrations get HTTP status 429 Too Many Requests. The Retry-After header says how many seconds to wait. Successful responses carry X-RateLimit-Limit and X-RateLimit-Remaining, so your integration can slow down before it hits the limit.

Whitelist an IP address

Requests from a whitelisted IP address are not limited.

  1. Go to Settings → Whitelisted IP addresses (German interface: Einstellungen → Freigegebene IP-Adressen).

  2. Click Add IP address.

  3. Enter the address or range and, optionally, a note (for example "CMS integration of our agency").

  4. Save. The change applies immediately.

Good to know:

  • Enter the public IP address, the one the internet sees. An internal address such as 192.168.x.x or 10.x.x.x, or a device's MAC address, does not help visitors. For an event, ask the venue's IT for the public IP address of the WiFi.

  • IPv4 and IPv6 addresses are accepted, and CIDR ranges up to /24 (IPv4) or /48 (IPv6), for example 203.0.113.0/24 or 2001:db8::/48. Larger ranges are refused.

  • You can whitelist up to 50 addresses or ranges.

  • You need the settings permission to see this page.

Time-limited access for events

If you do not know the IP address in advance, or visitors come through mobile networks, add a period instead. While a period is running, requests from every IP address are not limited.

  1. On the same page, under Time-limited access (German interface: Zeitlich begrenzte Freigabe), click Add period.

  2. Choose the start and end, in your own timezone. A period can last at most 72 hours.

  3. Save. The list shows whether a period is Active now or Scheduled.

You can have up to 10 current or upcoming periods. During a period bots are not limited either, so keep it as short as the event needs.

What always stays limited

A whitelisted IP address or a running period never lifts the limit on login, two-factor confirmation, password reset and API token requests. These protect your accounts against password guessing.

Not the same as Excluded IP addresses

Settings → Analytics → Excluded IP addresses only hides visits from your statistics. It does not change any limit. Whitelisted IP addresses only change the limit and do not affect statistics. See Analytics Settings in CamBuildr.

Did this answer your question?