HTTP Request - Body
Hey Y'all. I have a question on how the Body works in the HTTP Pipelines Channel. Before I begin I have everything working and set up correctly (Was able to do it in Postman and was able to do GE...
Forum Discussion
Looking at the api documentation, can you try to get/fetch a sub, add your id or email within the url path, not the body, and see if the remote api accepts your get request.
Based on the data you've outlined, it looks like you're trying to create a new user or update/insert one, then using post does require the body to have an email address (you have valid json), but the remote service doesn't like it. Is this email address already a current user?
What does postman show as the response? And, if you change the error option to custom, what happens in pipelines?
The email is already a Subscriber (me) but this is from the Mailerlite documentation: "If a subscriber already exists, it will be updated with new values. This is non-destructive operation, so omitting fields or groups will not remove them from subscriber."
When I did Custom Errors I got the same error message from the body
("body:{"message":"The email field is required.","errors":{"email":["The email field is required."]}}")
but Pipelines exempted the error
Here is my Postman response:
Here is my 200 ok using GET from Pipelines:
Trying many different things and I am completely stumped on why its not working.
Might just throw in a Ticket to Support.
Agreed. Everything looks good to me.
I really appreciate the help though! I will get back to you when I find the solution.
Thanks again!