Thank you for your question. It looks like the FormAssembly HTTP connector only sends out requests using the
application/x-www-form-urlencoded Content-Type whereas the API can only respond to data with the Content-Type of
application/json. I would first reach out to FormAssembly to see if you can send out a JSON request using their tools. If not, you may want to consider another tool for this or, as I mentioned, a custom middleware endpoint.
When I say custom middleware endpoint, I mean that you would set up a server that is able to listen for POST requests from FormAssembly, process the data using code on the server, and then make the requisite, JSON formatted, POST request to the Add Meeting Registrant API. However, if this is something you or your team isn’t familiar with it can be a challenging task which is why I recommend seeing what options FormAssembly can offer first.
Let me know if you have any questions.