302 Found

Found

The document has moved here.

Knowledge Base

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.

To see a complete list of characters and their encoded equivalents please see this Wikipedia article. For convenience we’ve provided a useful function if you’re building your URL within QuickBase.

Specifically the following characters are affected:

Character

Encoded Character Equivalent

! %21
*%2A
' %27
( %28
) %29
; %3B
:%3A
@%40
&%26
=%3D
+%2B
$ %24
,%2C
/%2F
?%3F
#%23
[%5B
]

%5D

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://YOURDOMAIN/db/DBID?act=API_AddRecord&_fnm_street_address=121%20M...

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
Type the characters you see in this picture. (verify using audio)
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.
302 Found

Found

The document has moved here.