302 Found

Found

The document has moved here.

API

Syndicate content
Options Parameter

You use the options parameter to further control the return of records. You can use any or all of the options, separating the options with a period. Here are the available options:

October 13th, 2009 - 2:10 PM
How QuickBase Views and Reports Relate to Queries

In the QuickBase UI, retrieved records are displayed in rows in a table, with the field data layed out in separate columns. This layout of record data is called a view.

October 13th, 2009 - 2:10 PM
Is There a Default View or Must I Construct a View?

Is There a Default View or Must I Construct a View?

October 13th, 2009 - 2:10 PM
How to Use Tickets: Tickets vs. Username and Password

If a user is accessing a QuickBase application through a web browser, once the call to API_Authenticate has been made successfully, the ticket cookie will be used automatically: there is no need to explicitly supply the ticket value as returned in the XML.

October 13th, 2009 - 2:10 PM
User Access and Your Application

This chapter covers the APIs application-level features that govern access. The calls that provide these features can be grouped as follows:

October 13th, 2009 - 2:10 PM
Secure Communications: Ticket and Application Token

on this link.)

topic for app tokens.

Optionally, you can create an app token directly from the call API_CreateDatabase if you used the createapptoken parameter. However, this can only be done at application creation time.

October 13th, 2009 - 2:10 PM
How Compromised Security Situations are Handled

If some user uses someone elses application token, and there is a complaint about this being unauthorized, the offending user will have access rights removed and the application token will be revoked.

October 13th, 2009 - 2:10 PM
API Calls That Dont Use the Application Token

The following calls use a ticket only, no application token:

October 13th, 2009 - 2:10 PM
Access to QuickBase (Login)

Login to QuickBase is provided through the API_Authenticate call, which returns a ticket and a ticket cookie. Just like a regular QuickBase login through the UI, the ticket by itself does not convey access to any applications. The application owner needs to assign an access role to the user first. (In addition to the ticket, your app needs an app token.)

October 13th, 2009 - 2:10 PM
The Typical User Management Cycle

After creating your application, tables and fields, and before inviting users to your application, you need to figure out what your system of roles should look like: what tables or fields should be accessed by which role, and what degree of access. All of this is done within Intuit QuickBase directly. The online help can lead you through the process.

October 13th, 2009 - 2:10 PM
302 Found

Found

The document has moved here.