If an answer is missing, check whether the website sent the form, whether the endpoint accepted it, and whether you are viewing the correct response dashboard.
Check these first
- Check that the endpoint and form are active, then copy the full submission URL into your website configuration.
- Publish the change and submit one clearly labelled test.
- Open that form's response dashboard and clear any filters.
- Check the endpoint request logs for a rejection or spam reason.
For developers: inspect the request
Open browser Developer Tools → Network and submit once. Look for a POST to the endpoint. No request usually means a validation or submit-handler issue. OPTIONS without POST points to a preflight failure. Opening the endpoint in the address bar sends GET and does not test submission.
| Result | What to check |
|---|---|
| 400 | Valid body and at least one non-empty field. Read the response message for field or value errors. |
| 401 / 404 | Full endpoint URL and current submit key; do not copy a masked key. |
| 403 | The message identifies domain, spam, availability, account, or form-limit restrictions. |
| 413 | Request body is too large. Reduce the submitted data. |
| 429 | Read the limit message and wait or review usage as directed. |
| 5xx / connection failure | Keep entered values and check for a saved response before retrying. |
Common questions
Why does the website show success without a saved response?
Check both response.ok and result.success before showing success. A filled hidden bot field can also return a success-shaped response without saving. Check the log reason and keep the endpoint's generated honeypot field empty.
Can the endpoint receive file attachments?
Use the Builder file-upload workflow for stored attachments. Adding a file input or encoding a file into a text field does not provide endpoint attachment storage.
Next checks: form integration, domain errors, or submission limits. Still stuck? Contact support with the form name, test time, status, and error message. Redact keys and visitor details.