To confirm, this issue is being encountered due to the fact that Captcha is enabled for the form you're attempting to pass submissions to via the API.
We do not support the use of Captcha when using the v2 or v3 endpoints. However, if you wish to use Captcha services, you can have these embedded on the page itself, not using the HubSpot functionality and this will work fine as we do not process any validation for incoming data. It is only once the data has been received that we process validation and in this case return 400 errors with the following:
{"status":"error","message":"The request is not valid","correlationId":"xxxx","errors":[{"message":"Form 'FORM_GUID' can't receive API submissions as Captcha (SPAM prevention) is enabled.","errorType":"FORM_HAS_RECAPTCHA_ENABLED"}],"requestId":"xxxx"}
Also, to touch on the Forum post you linked, the Solution that is marked there does not confirm that this should work, rather it states that the v3 endpoint is more flexible in it's functionality but it would still require investigation.
Feb 28, 20219:18 AM - edited Feb 28, 202110:09 AM
Contributor
Forms Api v3 - Captcha Handling
SOLVE
@DavidVendia No unfortunately there isn't.. I believe that Hubspot is forcing us to not be able to do this because they'd rather have you do a follow up email through their Automation Workflows, which however you can only do if you have their Marketing Professional package ($800/month).
That's the only logical thing I can point to because this design is so bad that it makes no sense
This is also a problem we are seeing. Spent a great deal of time integrating the Form API into our site setup and when I enable a "follow up" email everything breaks because of the forced captcha.
The form on our site is not an embedded HubSpot form, it's a custom form that pings a backend that uses the hubspot form API to submit the form submission (for conversions) in hubspot.
Is there any way to use follow up email functionality while using the form API?
To confirm, this issue is being encountered due to the fact that Captcha is enabled for the form you're attempting to pass submissions to via the API.
We do not support the use of Captcha when using the v2 or v3 endpoints. However, if you wish to use Captcha services, you can have these embedded on the page itself, not using the HubSpot functionality and this will work fine as we do not process any validation for incoming data. It is only once the data has been received that we process validation and in this case return 400 errors with the following:
{"status":"error","message":"The request is not valid","correlationId":"xxxx","errors":[{"message":"Form 'FORM_GUID' can't receive API submissions as Captcha (SPAM prevention) is enabled.","errorType":"FORM_HAS_RECAPTCHA_ENABLED"}],"requestId":"xxxx"}
Also, to touch on the Forum post you linked, the Solution that is marked there does not confirm that this should work, rather it states that the v3 endpoint is more flexible in it's functionality but it would still require investigation.
+1, I was using the api to handle custom form submissions, and also want to be able to use the follow-up email functionality and this is obviously blocking that currently
Thanks for the feedback, unfortunately, we cannot use the form embedded because we had to create a custom field validation to support the accessibility.
We disabled the Captcha and we will migrate the embedded form to API.
Thanks for the update @mdare_usablenet - I'll go ahead and flag this thread as resolved for now but feel free to get back to me should you have any issues in relation to migrating to the API.
Hi @Willson I'm having an issue that's related to this.
My issue is that I need my form to use the form API instead of the embeded one, and be able to use the follow-up email functionality. The problem is that to use the follow-up email functionality, it's required that we have reCaptcha enabled.
Is there a way I can use the follow-up email functionality and (not embeded) API forms?
@Willson We're having this same issue where we want to be able to use the follow up email function but we have it setup through the Forms API, which doesn't work when reCaptcha is enabled. We don't need to have reCaptcha enabled on the Hubspot Forms side because we have it already going on our website so it's redundant to do it twice. Why is Hubspot forcing us to use reCaptcha when we don't even need it and not allowing us to use the forms api?
In order to assist here, I'd need more information on the page, where you're seeing the error and what the error is specifically pointing to. Could you provide this so we can take a look?
- use something like Postman to test the API (so you don't have to make an actual form to submit).
- if you insert the information correctly, the POST will work and a new entry will show up on the form submissions.
- when you have everything working, edit the form, and add a follow up email.
This will trigger the form to require the captcha (that can not be disabled while you have any follow up email).
- back to Postman, try submiting again. This will fail with an error message saying:
{"status":"error","message":"The request is not valid","correlationId":"xxxxxxx-xxxxx-xxxxxxx","errors":[{"message":"Form 'xxxxxxx-xxxxxx-xxxx-xxxxxxx' can't receive API submissions as Captcha (SPAM prevention) is enabled.","errorType":"FORM_HAS_RECAPTCHA_ENABLED"}],"requestId":"xxxxxx-xxxxx-xxxxx-xxxxxx"}
This is clearly a blocker on hubspot's end. Would it be possible to make the captcha optional for API forms?
We would also like to have this feature enabled. We want to use the HubSpot Form Submission API including Captcha + Follow Up Mails without having to embed the HubSpot form. +1
^Exactly what @joaobelo said above. I would be more than happy to jump on a Zoom call and show you what is going on if you need more clarification as well @Willson
Thanks for the clarification with that, I am on the same page now.
However, this issue goes back to my original point. The Forms API does not support Captcha and this is a required step in order to use our Follow-up tool for Forms within HubSpot.
In this case, it means we cannot use our Follow-up tool with the Forms API and an alternative/external option is required.