topic Re: How to accommodate an HTTP request field name requiring a space in Workato Pros Discussion Board

How to accommodate an HTTP request field name requiring a space

JayMappus — Thu, 12 Oct 2023 14:24:12 GMT

Hi, I'm trying to send an HTTP request to an API endpoint using the Workato HTTP app "Send request via HTTP". The endpoint is expecting a field name of "First Name" (with a space) but it appears when creating the field name Workato does not allow spaces in the field names. I can only use snake case, such as "FirstName" or "First_Name". When the endpoint receives it in either format, I think it is interpreting it as "FirstName" or "First_Name" rather than the anticipated "First Name" and as a result does not accept the associated value as expected. And yes, the same thing happens with the Last Name. Other one-word field names are not having this issue.

I tried to manually edit the schema but get the following error when I try:

"Oops! Something went wrong

Field name should start with a letter and should not contain spaces or any special characters except `_`

Any advice? Maybe I'm off on my analysis of the issue? Thank you for your time and expertise.

Settings:

The request content type = Multipart form, Response content type = Text, Encoding = UTF-8

Re: How to accommodate an HTTP request field name requiring a space

gary1 — Thu, 12 Oct 2023 17:30:01 GMT

If you're referring to the response schema, I can't find a way around this issue directly in the HTTP action. Usually, you can use a JSON sample to work around this blocker, but when using a JSON sample with "first name", Workato automatically changes it to "first_name".

However, there are a couple things that do work...

First, you can access the key directly with bracket notation. This is a little clunky, but it works.

This message imitates the API response:

And then you can access it like this:

Output:

Second, (definitely the better option) you can feed a sample JSON with spaces into the JSON parser, and it will parse it without issue.

It still replaces the spaces with underscores, but this action provides data pills that retain the expected value.

Output schema:

So if I do this:

I get this:

Hope this helps!

Re: How to accommodate an HTTP request field name requiring a space

JayMappus — Fri, 13 Oct 2023 12:01:31 GMT

Thank you gary1 and for the great documentation! I will try your "better option" and report back.

Re: How to accommodate an HTTP request field name requiring a space

JayMappus — Fri, 13 Oct 2023 21:02:53 GMT

Gary1,

I wasn't able to get it to work but it's probably due to my lack of knowledge and understanding of what you are "saying". I tried the second option by first using the Parse JSON document action and then trying to use the result in a pill in the following HTTP post request schema but it still appeared in the receiving app as FirstName: Jay rather than First name: Jay. Am I way off course from what you were suggesting? Maybe you could dumb it down some more for me? Thank you J

Re: How to accommodate an HTTP request field name requiring a space

gary1 — Fri, 13 Oct 2023 21:35:50 GMT

It's a little confusing, but let's break it down. The core issue is the HTTP action won't parse the API response as-is, but the JSON Parser action will. This means you need to provide the JSON Parser with an example of the full response so it knows how to parse it, and in return it provides data pills to use in later recipe actions.

In both of our examples, we're only providing a snippet of the full response in the "sample document" field. Without seeing the actual full response from your HTTP action, I can't say exactly what you should put into the JSON Parser's "sample document" field, but what I recommend doing is copy/pasting the entire "body" JSON object from the HTTP action. (Sometimes this body is truncated which makes this trickier to do, but not impossible.)

Then, in the JSON Parser "document" input field, you should put the "body" data pill of the HTTP response.

Here's another example using the "Cat Facts" API (https://alexwohlbruck.github.io/cat-facts/docs/). For this example, let's pretend the API response is incompatible with the HTTP action, so we have to parse it in the JSON Parser.

HTTP action to call the API:

The HTTP action's output has a "body" value that is a "stringified" JSON:

Copy/paste that body into the "sample document" input field of the JSON parser. You can see that the JSON Parser is now providing all of data pills based on the provided sample:

Now, in the "document" field use the "body" data pill from the HTTP action. This is basically saying "I am providing you input data that is formatted exactly like the provided sample."

Finally, you can now use the output data pills from the JSON Parser (and they should have data):

... to get a result like this:

Good luck!

Re: How to accommodate an HTTP request field name requiring a space

JayMappus — Wed, 18 Oct 2023 12:17:18 GMT

Hi gary1,

Thank you for the break down. I think I see where the confusion is. Your explanation is for how to handle the HTTP response but my issue is with the HTTP request.

For the request I need to send a field with a field name of "First Name" so that the endpoint of the request can process it. "First Name" with a space is what the logic of the endpoint is expecting. However, Workato's HTTP request does not accommodate sending the name with a space. Instead it supports "FirstName" and "First_Name". When I use "FirstName" the field name of the request body schema (image attached) Request body using "FirstName"in Workato's HTTP appears to separate the First from Name (see image) in the input field name but when received at the webhook endpoint the name appears as "FirstName". Your solution would work if I controlled the logic at the receiving end but I do not and am trying to conform to the endpoint's standard.

Thank you again for your help.

Re: How to accommodate an HTTP request field name requiring a space

gary1 — Wed, 18 Oct 2023 20:39:09 GMT

Got it, thanks for all of the info. I think I have this figured out.

If you create the request body by providing a JSON sample, you can bypass this blocker. I tested this out using a recipe with an HTTP action using a multi-part form to make a POST call to an API endpoint, and then reviewing how the payload was received.

First, on the request body schema of the HTTP action I clicked "Use JSON" and to provide an example of how I want my payload to be structured:

I entered this:

It created this, which is misleading because it added the underscore to the label:

However, if you look at the schema, it has a details.real_name value of "test test" which is actually how the field gets encoded and sent in the API call:

Next I made an API call to an internal endpoint (with a value of "123").

I logged the message three different ways to be absolutely certain it was retaining the space:

To JSON:

To string:

Raw:

And then I even threw it into the JSON parser to ensure it parsed correctly:

And it did:

This is the way! Hope it gets you where you need to go.