Using Extended Character Sets in API Calls

A document by KCS Integration on behalf of eb807814eed7d7ac93aa32dcc227fd7fc6036751 on Feb 7, 2018Last modified by Vishal Sharma on Jun 26, 2018
Version 3Show Document
  • View in full screen mode

Issue Description
You want to use a non-standard character as a value (or part of a value) in an API call (e.g. é), but when you put it in, the call does not work (either failing with an error or not posting the expected character).


Issue Resolution
Encode the extended characters using ASCII URL encoding for UTF-8. There are sites that will perform this encoding for you, here is one: For example: making this call, " https://<munchkinid>{folder id}/tokens.json?access_token=<accesstoken>&name=TestName&value=Hello+%C3%A9marketo&type=text&folderType=Folder " will create a token called "TestName" with a value of "Hello émarketo"


Who This Solution Applies To
API Users

Is this article helpful ?