Some doubts around certain requested URLs

Hi David,another ask for you . i must consume a webservice with a proproetary syntax (see bold words) (it is http://loopback.io/) but i think that there are some misunderstanding with your variables trancodification at runtime. can you help me?

HttpClearData "wslogin" HttpSetHeader "wslogin" "Content-Type" "application/json" HttpSetUrl "wslogin" "http://xxx.xxx.xxx.xxx:3000/api/Utentipwaapps?access_token=[token]&filter<strong>[where][0][email]</strong>=paolo@gneral-soft.com" HttpExecute "wslogin"

[token] is a variable and it is correctly replaced at runtime.tanks paolo

Hello Paolo,

It's difficult to help without more details. For example, I am not quite sure if the "HttpSetHeader" is really needed. But anyway must work. On the other hand, about the URL that you try to conform, certainly I can see something "rare"

access_token=[token]&filter[where][0][email]=paolo@gneral-soft.com

Maybe is a mistake when copy the URL and variables, but, this have not too much sense: [where][0][email]

Maybe you want to conform an URL like the below one?

access_token=[token]&filter[where]&email=paolo@gneral-soft.com

That URL must work, in principle. Maybe you can use the EncodeURI action, but, I am not sure.

Finally, the point is, what is the result that you expect and what is the result that you get? Some error message?

---

according to the loopback manual

REST API

In the first form below, the condition is equivalence, that is, it tests whether property equals value. The second form below is for all other conditions.

filter[where][property]=value filter[where][property][op]=value

For example, if there is a cars model with an odo property, the following query finds instances where the odo is greater than 5000:

/cars?filter[where][odo][gt]=5000

For example, here is a query to find cars with odo is less than 30,000:

/cars?filter[where][odo][lt]=30000

the sintax is rigth... i have sent you an email with the full http GET request. the result is a json object

Hello Paolo,

I am not quite sure about what the problem can be. Maybe you have an problem with the variables in the URL? Certainly, if we must place something like "[this]" in the URL, since "[this]" appear as an AB variable, maybe we can have some problem. Maybe a possible solution can be to use HTML entities instead of the brackets "as is".

I want to shown here the HTML entities, however, they are converted to the brackets... so I can't shown to you here as I wanted. But take the idea: instead of use the brackets "as is", you must replace the brackets with their HTML entity representation, so AB don't take it as variables.

If something like that don't work as expected, maybe you need to prepare some "bridge" between the API that you want to use and your app, using some server script placed in your app's server. So you can use URLs without the "brackets" (all of these suposing this is the problem, I am not sure!), and then your server script made the appropriate calls to the API (here we can use "brackets" without problems) and provide to the app the API response.

But I must insists, Paolo, I am not sure if the brackets are the problem or not. Do you get what you wanted? If not, do you get some error message?

---

i have foud the solution.. i can use json request insteed

SetVar "chiamata" "filter={\x22where\x22:{\x22email\x22:\x22paolo@general-soft.com\x22}}" "String" HttpSetUrl "wslogin" "http://xxx.xxx.xxx.xxx:3000/api/Utentipwaapps?[chiamata]" HttpSetHeader "wslogin" "Content-Type" "application/json" HttpSetHeader "wslogin" "X-Access-Token" "[token]"

how i can create a json string in ap?

Hello Paolo,

May something like the below can be enough:

NewObject "[MyObject]" ObjectSetProp "[MyObject]" "name" "Peter" ObjectSetProp "[MyObject]" "lastname" "Parker" StrSerialize "[MyObject]" "[Result]" Alert "" "[Result]"

In the Result variable you have an JSON string representation of MyObject.

---

a possible solution to my forst post is change [ with \x5b

 and ]  whit \x5d

in HttpSetUrl

 before call HttpExecute

David could be interesting implement this in ap ?

you do something simmilar with \x22  for "

thanks paolo

Hello Paolo,

I think that can understand what you wanted, however, I am not sure if something like that can be good. Commonly we can use variables, so, maybe it's not a good idea to replace the brackets in all the cases. Use brackets "as is" is probably more rare than use variables.

---