Forum Discussion

demosoapuser's avatar
demosoapuser
Occasional Contributor
8 years ago

Symbols or special characters are not recognized as string and is converted to ascii code

I'm tying to send a  request using an email in the parameter template. "@" sign is converted to %40. Is there any way to send it as a string? All my data is in email format
nmrao's avatar
nmrao
Champion Level 3
Is it that first API response has @ or ascii? And you only have problem in the second API? Also in the second API, is it part of query parameter or template parameter? Details would help.
demosoapuser's avatar
demosoapuser
Occasional Contributor
8 years ago

The usual data in the response is like "abcde" but now all data is in email format. I'm using that data on parameter template for the 2nd api call

  • demosoapuser's avatar
    demosoapuser
    Occasional Contributor
    8 years ago

    I wasn't able to find solution for this. Again, data returned on the 1st api is in email format with "@" sign and when I use this value on the 2nd api, "@" sign is being sent as Ascii and not as string.

    • Debz's avatar
      Debz
      Contributor
      8 years ago

      Hi, are you already using Ready!API 2.0 or an older version? For older versions, I've seen in the forums before that using Lucida Sans Unicode font or setting Preferences > UI Settings to default look and feel fixes some issues with special characters. Then one of my coworkers suggested to select the REST test step, check on the Properties, and click on the field for the encoding. You have the option there to select ISO or UTF. You might want to try those. The last one worked on our end when foreign characters were getting converted to weird characters. Maybe it will also work for the "@" sign?