A limit can come from repeated requests, a daily allowance, your account's plan, or a restriction set on the form. Read the message before retrying.
Choose the right next step
| Message | Action |
|---|---|
| 429: too many submissions in a short time | Stop repeated clicks or automation and wait for the indicated retry interval. |
| 429: today's endpoint limit | Review daily usage. A rapid retry will not restore the allowance. |
| 403: account plan limit or expired subscription | Ask the account owner to review usage and subscription details. |
| 403: form submission restriction | Review this endpoint's configured submission restrictions. |
For developers
For short-term JSON rate limits, read data.retry_after_seconds. The response also includes Retry-After, but cross-origin browser code may not be able to read that header. Daily-limit responses may not include a short retry interval. Keep the form values and avoid automatic retry loops.
Common questions
Where can I find my exact allowance?
Check your account's usage and plan details, plus this form's restriction settings. A plan allowance and short-term request protection are different limits.
Should I resubmit or delete responses to clear a limit?
Do not delete responses to troubleshoot usage limits. Wait when the message gives a retry interval; otherwise address the account or form setting. After a timeout, check for an existing saved response before submitting again.