Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

JSON Payload Sending as octet-stream

Erik Nelson
Kilo Sage

Hello all,

 

I've more-or-less successfully built my first action. It's taking catalog inputs and generating a JSON Payload then sending it to an endpoint via a REST step. I can get the data to load and send, but the odd part is, it's sending as an octet-stream rather than a simple JSON file ("$content-type": "application/octet-stream" as opposed to application/json. I'm not seeing anything on my side in the Flow/Action that indicates it is/should be doing that. Can anyone provide some guidance on where I check/set this value? I am using the JSON Builder step and the REST step.

 

Thank you,

Erik

1 ACCEPTED SOLUTION

Erik Nelson
Kilo Sage

For those who are looking for a quick answer to this, it gets set as a Header of the REST Step. If you don't put one, it looks like it defaults to application/octet-stream. If you set it in the Header to have a Name/Value pairing of "content-type" and "application/json", it will send in the json format without the added encryption.

View solution in original post

2 REPLIES 2

Erik Nelson
Kilo Sage

For those who are looking for a quick answer to this, it gets set as a Header of the REST Step. If you don't put one, it looks like it defaults to application/octet-stream. If you set it in the Header to have a Name/Value pairing of "content-type" and "application/json", it will send in the json format without the added encryption.

Just wanted to kudos to you, for answering your question with the helpful answer!