Character Escaping / Encoding

This documentation is for LiquidPlanner New:

All Your Calls Should be URL-encoded

While most programs support encoding automatically, it’s worth noting that certain characters in a filter string may require manual URL-encoding (if your tool doesn’t support automatic encoding).

Make sure all of your API calls are URL-encoded. A filter string such as?itemType[is]="packages”would change to?itemType%5Bis%5D=%22packages%22when encoded.

If your filter string has not been escaped, you’ll receive a 400 error message as explained under Errors & Resolutions.

What’s Next