Update data ext
update_data_extSets the value of a custom field (owner_id 0) or private extension (your GUID) on a list object or transaction. The object needn't have a value yet: on QuickBooks Enterprise 24.0 (2026-10-10) this set a custom field's first value on a new sales order, so you don't need data_ext.create first. The definition must reach the object's type: a custom field defined on Customer also reaches credit memos, estimates, invoices, sales orders and sales receipts. It can't clear a value; delete the value instead.
The data_ext_mod wrapper from qbXML is also accepted. Returns the v2 request to send, and the webhook payload QuickBooks' answer arrives in (this operation's response_json: its data shape and the status codes to handle).
Possible errors (error.code / error.type; the call result explains each): 1030 unsupported_request, 3000 invalid_object_id, 3040 invalid_amount, 3070 string_too_long, 3120 object_not_found, 3140 invalid_reference, 3150 missing_element, 3170 cannot_modify, 3175 in_use, 3176 locked, 3200 stale_edit_sequence, 3210 invalid_value, 3220 not_authorized, 3231 request_not_processed, 3250 feature_not_enabled, 3260 insufficient_permission, 3261 personal_data_access_denied, 3262 payroll_subscription_required, 3263 read_only_access, 3264 merchant_services_subscription_required
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"data_ext_name": "<data_ext_name>",
"data_ext_value": "<data_ext_value>",
"owner_id": "<owner_id>"
},
"name": "update_data_ext"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| txn_id | No | `txn_id` is the unique QuickBooks identifier for a transaction. Use it to reference that transaction in later requests. Choose exactly one of: the set (`list_data_ext_type`, `list_obj_ref`), or the set (`txn_data_ext_type`, `txn_id`, `txn_line_id`), or `other_data_ext_type`. Members of a set combine with each other, not with the other choices. | |
| owner_id | Yes | `owner_id` identifies who owns the data extension. Use 0 for QuickBooks custom fields that appear in the UI, or use a GUID for private extensions owned by an app. | |
| request_id | No | Your own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`. | |
| txn_line_id | No | Identification number of the transaction line. (`txn_line_id` is supported as of v2.0 of the SDK. With qbXML v1.0 and v1.1, `txn_line_id` is always returned as zero.) Choose exactly one of: the set (`list_data_ext_type`, `list_obj_ref`), or the set (`txn_data_ext_type`, `txn_id`, `txn_line_id`), or `other_data_ext_type`. Members of a set combine with each other, not with the other choices. | |
| list_obj_ref | No | Refers to a list object. In a DataExtAdd request, the list object ref must be the same type as the type specified in `list_data_ext_type`. Choose exactly one of: the set (`list_data_ext_type`, `list_obj_ref`), or the set (`txn_data_ext_type`, `txn_id`, `txn_line_id`), or `other_data_ext_type`. Members of a set combine with each other, not with the other choices. | |
| data_ext_name | Yes | The name of the data extension. If this is a custom field, `data_ext_name` will be visible as a label in the QuickBooks user interface. | |
| include_qbxml | No | Also return the qbXML this compiles to, for debugging. Not part of the v2 request. | |
| data_ext_value | Yes | The data in this field. The maximum length of `data_ext_value` will depend on the `data_ext_type` of this data extension. | |
| txn_data_ext_type | No | The type of transaction that the data extension belongs to. Choose exactly one of: the set (`list_data_ext_type`, `list_obj_ref`), or the set (`txn_data_ext_type`, `txn_id`, `txn_line_id`), or `other_data_ext_type`. Members of a set combine with each other, not with the other choices. | |
| list_data_ext_type | No | The type of list object (e.g. Customer) that this data extension is attached to. Choose exactly one of: the set (`list_data_ext_type`, `list_obj_ref`), or the set (`txn_data_ext_type`, `txn_id`, `txn_line_id`), or `other_data_ext_type`. Members of a set combine with each other, not with the other choices. | |
| other_data_ext_type | No | Not supported. Choose exactly one of: the set (`list_data_ext_type`, `list_obj_ref`), or the set (`txn_data_ext_type`, `txn_id`, `txn_line_id`), or `other_data_ext_type`. Members of a set combine with each other, not with the other choices. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Replace {connection_id} with the customer's connection. | |
| body | Yes | The JSON body: the arguments you passed. | |
| qbxml | No | The qbXML it compiles to. Only with include_qbxml. | |
| method | Yes | ||
| headers | Yes | Send with the request. Resent unchanged when no 201 came back, it answers with the request already queued. | |
| webhook | Yes | JSON Schema of the payload POSTed to webhook_url once QuickBooks answers, with this operation's response_json (data shape and status codes). |