Troubleshooting

Real cases from Farvane's pipeline, not a generic list. If you need the exact technical detail for a response code, check the API reference.

The email isn't arriving

First check the spam or promotions folder of the email client — that's the most common cause. If it's not there, open your form in the dashboard, Settings tab, and confirm the target emails are correct: a typo there means the submission is processed but never reaches anywhere. If your plan requires domain restriction and your form has an allowed-domains list configured, check that the domain you're submitting from is in that list — if it isn't, the API responds 403 instead of accepting the submission, and the email never gets sent.

My submission gets marked as spam

The hidden botcheck field is the anti-spam trap (honeypot): it must always arrive empty. A very common cause of false positives is a password manager that autofills every field in the form, including this one. Every Farvane snippet already includes autocomplete="off" and tabindex="-1" on that field precisely to prevent this — if you copied the form a while ago or edited it by hand, check that both attributes are still there.

I get a 429 error

This code covers two different limits, depending on the message. "Demasiadas peticiones" ("too many requests") is the 20-requests-per-minute limit for the same access_key + IP — an anti-abuse protection that resolves itself after a minute. "Límite de envíos mensuales alcanzado" ("monthly submission limit reached") means your form used up your plan's monthly submission quota this month.

Check Billing & Usage in the dashboard

I get "access_key inválido o ausente" or "Formulario no encontrado"

The API returns 400 with one of these messages in two cases: the access_key is not a valid UUID (check that you copied it in full, with no extra spaces or characters), or it belongs to a form that no longer exists, for example if you deleted it from the dashboard. Copy the access_key again from the Settings tab of the corresponding form.

Still stuck? Check the API reference to see exactly which response code you are getting.