http_api

Syndicate content
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
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
User Setup (Provisioning)

In order for someone to use a QuickBase application accessed through the API, they will need to be assigned a role within that QuickBase application by the application administrator. The roles are set up in QuickBase to provide varying kinds of access.

API_ProvisionUser .)

October 13th, 2009 - 2:10 PM

© 1997-2014 Intuit Inc. All Rights Reserved.

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