Any web page or outside program that accesses Quickbase through the Quickbase HTTP API should use application tokens. This includes some Quickbase add-ons, like the Forms wizard (which lets you add a form to any web page and have it populate your Quickbase) and other automated wizards that are available in the Quickbase KnowledgeBase.
A token is an extra string of characters a programmer must insert in an API call. That string must match application tokens assigned to the application that the API call targets. Add-ons come with a token code.
To make the add-on work, do one of the following:
-
Disable the tokens – Disabling tokens is a workaround solution and means that you lose the additional level of security that tokens supply.
-
Assign the add-on's token to the application – Each add-on has its own token. Just assign the add-on token to the application and API calls that the add-on makes to your application will work.
Note: Though exact forms use the Quickbase API, this feature does not require application tokens. In fact, to use exact forms, you must leave tokens disabled, or, if you require tokens for the application, disable them.
The following table lists add-ons and their tokens:
|
Feature |
Token |
|---|---|
|
Forms Wizard |
cwfcy7gdzqrsyncqbi2bn4u4kr |
|
Note: Quickbase has a Copy Master and Detail Records feature. If your application is not already using the wizard, use the Quickbase feature instead. |
bqipbngdfsd6drc64a958wz4aua |
To copy a token and assign it to the application with the add-on:
-
Click Assign Existing Application Token.
-
Paste or type in the application token.
Alternatively, click Choose Existing Token, and choose a token from the dropdown.
-
Type in a description to remind you what the token does.
Name it for the add-on, like Forms Wizard, for example.
-
Select the Ok to Copy checkbox to copy this token when you copy the application.
-
Click OK. Assignment is complete. API calls containing this token can now interact with the application.