How to Edit Records in Quickbase via API

Quickbase API_EditRecord is a powerful tool for automating record updates and building efficient workflows. Whether you're creating approval buttons, triggering webhooks, or writing scripts, mastering this API can significantly improve your app’s functionality.

What is API_EditRecord in Quickbase?

API_EditRecord is a Quickbase API endpoint used to modify existing records by specifying:

• The target table
• The record ID (RID) or key field
• The fields and values to update

It works through GET requests (URL-based) or POST requests (not covered here but similar in structure).

Common Use Cases for API_EditRecord

You can use API_EditRecord in Quickbase to:

• Create custom buttons that update multiple fields at once
• Trigger updates using Quickbase webhooks
• Perform client-side or server-side scripting
• Automate workflows like approvals or status changes

Example Use Case: Approval Workflow

You can build a button that:

• Marks a record as Approved
• Logs the approval date
• Captures the approver (current user)

This creates a seamless, automated approval process.

How to Use API_EditRecord (Step-by-Step)

Step 1: Define the Target Table

The base URL structure is (see image below)

• target_domain = your Quickbase realm
• target_dbid = the unique ID of your table (found in the URL after /db/)

Step 2: Add the API Action

To edit a record, append: ?a=API_EditRecord

Example (see image below)

Step 3: Include Authentication

You must authenticate the request using one of the following:

• User token (recommended) (see image below)

• App token (if required) (see image below)

Step 4: Specify the Record ID (RID)

To identify which record to edit: &rid=12345

Alternatively, you can use a custom key field if configured.

Step 5: Set Field Values

Use field IDs (best practice) to update values: &_fid_6=Approved&_fid_7=2024-01-01&_fid_8=JohnDoe

• _fid_6 = Approval Status
• _fid_7 = Approval Date
• _fid_8 = Approver

Why use Field IDs?
Field IDs do not change, while field names can—making your API calls more stable.

Step 6: Full API_EditRecord Example

Step 7: Test Your API Call

Paste the URL into your browser or trigger it via:

• A Quickbase button
• A webhook
• A script

If configured correctly, the record will update instantly.

What are the Best Practices for API_EditRecord

• Use field IDs instead of field names
• Use user tokens for authentication
• Test in a sandbox or test table first
• Keep URLs clean and properly encoded
• Document your field mappings

Advanced Tip: Using the clist Parameter

Quickbase supports the clist parameter to return specific field values in the response:

This allows you to control which fields are returned in the XML response.

Quickbase API_EditRecord is a powerful tool for automating record updates and building efficient workflows. Whether you're creating approval buttons, triggering webhooks, or writing scripts, mastering this API can significantly improve your app’s functionality.

Top FAQs about Quickbase API_EditRecord

1. What does API_EditRecord do in Quickbase?

API_EditRecord updates a single record in a Quickbase table by modifying field values using an API request.

2. How do you edit a record in Quickbase using API?

You edit a record by calling ?a=API_EditRecord, passing authentication, specifying the record ID, and defining field values.

3. Can API_EditRecord update multiple fields?

Yes. You can update multiple fields in one request by adding multiple _fid_#=value parameters.

4. What is the difference between RID and key in Quickbase?

• RID = default Record ID#
• Key field = custom unique identifier

Both can be used to identify records in API_EditRecord.

5. Do you need authentication for API_EditRecord?

Yes. You must authenticate using a user token, ticket, or app token.

• Author: Alistair Marsden
• Title: Solution Consultant | Quickbase
• Email: amarsden@quandarycg.com
• Date Updated: 03/202026