I am currently using the v2 Forms API, but ran into an issue where forms with captcha enabled returns an error.
Switching to v3 does not seem to return an error if captcha is enabled – which is good – but, since captcha handing is not mentioned in either the v2 or v3 documentation I'm not sure if this is what's intended.
I am hoping to get confirmation that this is the intended result and it will not break in the future. Any information would be helpful.
I've only found one other topic reporting reCAPTCHA issues with the v2 Forms API. Does this sound like the issue you encountered? If so, what error was returned? Can you send me a link to the HubSpot form you were testing?
I don't have specific insight into reCAPTCHA-related support in the v3 Forms API, but it was designed to be more flexible and powerful than the second version. Since it's in stable release, I can confirm the team doesn't plan to make any major updates to it, so the behavior you're seeing should not change in the future.
Thanks for the feedback, @Adam_Volkman! This is super helpful. We're actually in the middle of auditing all of our developer documentation so I will make a note to have reCAPTCHA mentioned (I personally never knew this v2 restriction existed).
Yes, that appears to be the same issue we ran into. Sorry for the lack of detail - I was mostly concerned with the new api. Here is the html response we received when trying to submit to a form with reCAPTCHA enabled.
It appears there's no support for this, since it says "If you've manually integrated this form, please turn off reCaptcha". If that's the case, it's fine, but I would recommend noting this restriction somewhere in the api documentation. It could help avoid some confusion for developers in the future.
Upgrading to the v3 Api works for us as a solution and I'm glad to hear it should continue to work with reCAPTCHA enabled forms. Again, it would be helpful to note in the docs that reCAPTCHA will be ignored for api submissions (or however the api handles it). When working with APIs it's not ideal to have to make assumptions, since it can come back to bite you – as it did for us
I've only found one other topic reporting reCAPTCHA issues with the v2 Forms API. Does this sound like the issue you encountered? If so, what error was returned? Can you send me a link to the HubSpot form you were testing?
I don't have specific insight into reCAPTCHA-related support in the v3 Forms API, but it was designed to be more flexible and powerful than the second version. Since it's in stable release, I can confirm the team doesn't plan to make any major updates to it, so the behavior you're seeing should not change in the future.