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.

How do I have a single button perform multiple QuickBase HTTP API operations?

Every API call includes an optional rdr parameter. This tells the browser what page to go to when the API action completes successfully. Within the limit of a URL you may include as many API commands as you want. To accommodate all browsers, keep your URL length to roughly 1,000 characters when submitting a GET request. You should be safe using a 2,000-character limit with modern browsers, however.

Important: You must encase every redirect parameter in a URLEncode function. Without this, QuickBase ignores that API statement.

An example is shown below. To see this demonstrated, please see this video.

URLRoot() & "db/" & DBid() & "?act=API_EditRecord&_fid_16=VALUE1&apptoken=XXXXXXXXXXXXXXXXXXXXXXXXXXXX&rid=" & [Record ID#] & "&rdr=" & URLEncode(URLRoot() & "db/" & [_DBID_CHILD_TABLE] & "?act=API_AddRecord&_fid_6=" & [Record ID#] & "&_fid_8=VALUE2&apptoken=XXXXXXXXXXXXXXXXXXXXXXXXXXXX&rdr=" & URLEncode(URLRoot() & "db/" & DBid() & "?a=q&qid=1"))

Note: QuickBase recommends that you use application tokens for all API calls for security purposes. Read more about tokens in the QuickBase online help.

Comments

When using multiple rdr

Something to keep in mind when using multiple rdr is you must open a new URLEncode() for each rdr URL.  Just wrapping all rdr's with one URLEncode() will not work, nor will wrapping each individually.

 

Example of how to get multiple rdr's working in one formula:

 

URLRoot()&"db/"&[_DBID_EXAMPLE]&"?a=API_EditRecord&_fid_2=SomeValue&rid="&
[SOME LOOKUP REF]&"&rdr="&

URLEncode(URLRoot()&"db/"&Dbid()&"?a=API_EditRecord^_fid_1=SomeValue^rid="&
[Record ID]&"&rdr="&

URLEncode(URLRoot()&"db/"&Dbid()&"?a=q^qid=1")))

 

Notice there are two redirects each beginning with URLEncode(), however they are not closed out until the end of they statement.

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.