APIs

Syndicate content

You can find the QuickBase HTTP API guide here:

http://www.quickbase.com/api-guide/index.html

You can always access the API guide using the HTTP API Documentation link on the main page of the QuickBase Innovation Network. You can also access the API guide from the QuickBase online help.

February 5th, 2009 - 6:02 PM

The API enables you to do all of the following:
- Add records
- Edit existing records
- Change permissions on a QuickBase application
- Get and modify the schema of an application
- Change the properties of a field
- Find database IDs by database name
- Clone a database
- Get records one at time or by executing queries
- Delete records
- Manage Users and Roles

February 5th, 2009 - 6:02 PM
Tags:

The only API call that returns a ticket as a cookie is the API_Authenticate call. So if you want to do several API calls one after another you either have to supply a username and password for each call or you can start with the API_Authenticate call and it will return a ticket as a cookie.

February 5th, 2009 - 6:02 PM

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.

February 5th, 2009 - 6:02 PM

No anyone who programs in an environment that supports HTTP POSTs and GETs can make use of the QuickBase API. This includes but is not limited to C, C++, Python programmers as well as Cold Fusion developers.

February 5th, 2009 - 6:02 PM

For all QuickBase users, you can find the database ID of a table in the address bar of your browser when you're looking at any page of the table. The home page of all QuickBase applications has a DBID that does not refer to any of the tables in the application. You must navigate to a form or view that is specific to your table to cause the proper dbid to appear in your browser's address bar.

February 5th, 2009 - 6:02 PM

The QuickBase API allows Web page designers, Perl, Java, and Visual Basic developers to access QuickBase from their pages or code.

February 5th, 2009 - 6:02 PM

If everyone using a particular QuickBase table or application package sets their browser's character encoding (on Internet Explorer click on the "View" menu and select "Encoding") to the same setting then everything will be displayed and edited consistently whether the setting is a single byte character encoding like IS0-8559 or Western European (Windows) or a multi-byte character encoding like Un

February 5th, 2009 - 6:02 PM

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.

February 5th, 2009 - 6:02 PM

Please see our About Field Types help topic for more information.

February 5th, 2009 - 6:02 PM

© 1997-2014 Intuit Inc. All Rights Reserved.

Online Database VeriSign Secured Web Based Software TRUSTe Certification Online Database SSAE Audit