Our Knowledge Base covers a wide variety of technical topics, from the basic to the complex.
What are the rules for encoding URLs for the QuickBase HTTP API?
In your URL commands to QuickBase, you must encode any special characters within the query string. This applies only if those characters are in either a field name or value of your attribute.
Specifically the following characters are affected:
Encoded Character Equivalent
! %21 * %2A ' %27 ( %28 ) %29 ; %3B : %3A @ %40 & %26 = %3D + %2B $ %24 , %2C / %2F ? %3F # %23 [ %5B ]
Note: If you intend to use a XSL stylesheet to display your XML results, you cannot use ampersands in that URL. Instead use the caret character in its place. The caret’s URL encoded value is %5E.
To demonstrate this usage, if you had a QuickBase table with four fields labeled “Street Address”, “No of Residents”, “Percent Occupied” and “Description” with respective values of “121 Main St.”, “12”, “13%” and “Fred & Mary live here?^^” , your API_AddRecord command would look like this:
https://mycompany.quickbase.com/db/DBIDact=API_AddRecord&_fnm_street_address=121%20Main%20St. &_fnm_no_of_residents=12&_fnm_percent_occupied=13%25&_fnm_description=Fred%20%26%20Mary%20 live%20here%3F%5E%5E