Update / Create Marketo token API

Question

I am wondering why the tokens through API should be passed as POST x-www-form-urlencoded ONLY, and not as JSON. This brings many issues. One issue, among others, is when you encode the URL the "value" lenght must be short and nearly just plain text, not URL and/or HTML, otherwise you will pass the 2048 character limit that some services like Google has for URLFetch, leaving this end point nearly usless.
I did try compressing the URL through gzip, shortening the URL thoroug few services, but the Marketo end point refuses to accept those, so the question is why , why not to accept a JSON payload?

Diego_Lineros2 · Accepted Answer

I found the solution, I think it was a long night...

DON't do that

// Create the API endpoint URL with placeholders
var apiUrl = "https://xxx-xxx-xx.mktorest.com/rest/asset/v1/folder/" + program + "/tokens.json?folderType=Program&name=" + name + "&type=" + type + "&value=" + value;

// Compress the API URL
//var compressedApiUrl = compressUrl(apiUrl);

// Check if compressed API URL length exceeds 2082 characters
if (apiUrl.length > 2082) {
Logger.log("Compressed API URL length exceeds 2048 characters. Skipping this row.");
var ui = SpreadsheetApp.getUi();
ui.alert( "URL Length Exceeded " + apiUrl.length, "URL length for Row " + i + " exceeds 2082 characters. Skipping this row.", ui.ButtonSet.OK);
continue; // Skip this row
}

// Make the API request with the Marketo access token
var response = UrlFetchApp.fetch(apiUrl, {
method: "post",
contentType: "application/x-www-form-urlencoded",
headers: {
"Authorization": "Bearer " + accessToken

DO that

// Prepare the payload as a URL-encoded string
    var payload = "folderType=Program&name=" + name + "&type=" + type + "&value=" + value;

    // Make the API request with the Marketo access token
    var response = UrlFetchApp.fetch("https://xxx-xxx-xxx.mktorest.com/rest/asset/v1/folder/" + program + "/tokens.json", {
      method: "post",
      contentType: "application/x-www-form-urlencoded",
      headers: {
        "Authorization": "Bearer " + accessToken
      
      },
      payload: payload
    });

SanfordWhiteman · Answer

Also bear in mind that while the endpoint formally expects application/x-www-form-urlencoded, it is implemented to support not only multipart/form-data with UTF-8 parts but also UTF-8 IRIs, not just URIs.

There’s no reason for these encodings to be a barrier vs. JSON.

(Really unlikely that JSON would be more space-efficient than an IRI in any practical scenario. That is, the difference in byte length would be at most a handful of bytes in either direction.)

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded