Hello @████████

Unfortunately, I was never able to resolve the CORS/CORB issue in order to contact this API or any other API from within LFForms.  I probably spend 100+ hours researching, testing, tweaking, and never getting it to work.  Untimately, we pursued another avenue to deal with the census tract data we needed.

However, I more recently found a need to try to work with a couple other APIs, that of course had similar CORS/CORB issues, but were a much more pressing need.  Ultimately, I ended up building my own API (using C# in Visual Studio) and hosting that on the same server that runs LFForms.  LFForms passes information to/from my API, which in turn passes information to/from the third party API.  Because LFForms is communicating with an API on the same server that it is housed on, the CORS/CORB issue never arises.  It's a giant pain to set-up, and I'm limited to the specific items of the third-party API which I have already identified as needed for the LFForms process (because adding anything else means modifying my API to add it instead of just adding new calls in LFForms).

This isn't a small solution or one for someone without at least intermediate coding skills - but it works well if you can do it.

An easier solution - if you don't need the functionality available directly within LFForms, but could run in-between tasks - you might be able to do the API calls from within LFWorkflow and pass the resulting data back to LFForms.