---
title: "Application Token step"
slug: "application-token-step"
updated: 2026-10-09T18:23:01Z
published: 2026-10-09T18:23:01Z
canonical: "help.quickbase.com/application-token-step"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.quickbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Application Token step

The **Application Token** step asks for a Quickbase application token for the app you're setting up. If your app requires application tokens, the button the wizard creates to start a run needs one.

## When the step appears

- **Exact Forms Plus, XL Docs, and PDF Stamper**: when you choose **Bulk Document Generation** in **Select the Setup Type**. The step is added just before **Finish**. Switching back to **Single Document Generation** removes it.
- **PDF Merger**: always, as the last step after **PDF Merger Setup**.

## The Application Token step

1. **Application Token** (optional). A text box. Paste the application token for your app.
2. **The explanation.** Below the box, the wizard shows: *The Add-On you are setting up may require an Application Token to run if your application is configured to require Application Tokens. Please supply the Application Token and press* **Next** (or **Finish**, when this is the last step)*. If your application requires a token and you didn't provide one, you'll need to add it in the specified fields.* A link to a video about getting an application token follows.

The wizard doesn't check the token. Select **Next**, or **Finish** if this is the last step.

## What the token is used for

The wizard adds the token to the **apptoken** parameter of the button that starts a run, for example **Execute Batch** on the batch processing table, or **Execute PDF Merger** on the table you chose for PDF Merger. The button updates the record through the Quickbase API to start the run, and if your app requires application tokens, that call needs a valid one.

- If your app doesn't require application tokens, leave the box empty.
- If it does, create a dedicated application token for the extension in your app's settings and paste it here, rather than reusing a token that other integrations depend on. That way you can change it without affecting anything else. See [App tokens](https://help.quickbase.com/docs/app-tokens) in the Quickbase help.
- If you left the box empty and your app requires tokens, add the token to the **apptoken=** parameter in the button's formula later.

The token is part of the button's formula, so anyone who can see the field's properties can read it.

## Single document generation: add the token yourself

With **Single Document Generation** (and the Exact Forms Plus native template), the wizard doesn't show this step. It still creates a button that starts a background run on the table you chose: **Execute EFP Batch**, **Execute XL Docs Batch**, or **Execute PDF Stamper Batch**. That button's formula has an empty `apptoken=`.

If your app requires application tokens, add yours to that line of the field's formula:

1. In Quickbase, open the table's field list and edit the **Execute … Batch** field.
2. In the formula, find the line `& "&apptoken="`.
3. Add your token after the equals sign, for example `& "&apptoken=your_app_token"`, and save the field.

If your app doesn't require application tokens, you don't need to change anything.