Find build assemblies
find_build_assembliesFilters BuildAssembly transactions by the specified filter criteria.
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, 3150 missing_element, 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, 3264 merchant_services_subscription_required
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "find_build_assemblies"
}
}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 at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`item_filter`, `max_returned`, `modified_date_range_filter`, `pending_status`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices. | |
| iterator | No | Page through every match: QuBe Sync asks QuickBooks for each page in turn and sends each to your `webhook_url` as it arrives, all with the same `id`. On by default, with pages of 100 records; send `iterator=true` with `max_returned` for another size. Off when you send `iterator=false` (every match in one answer) or `max_returned` alone (at most that many, in one answer). It pages a filtered query only: with `ref_number`, `ref_number_case_sensitive` or `txn_id` every match comes back in one answer, so leave `iterator` out. | |
| owner_id | No | `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. | |
| meta_data | No | Use the `meta_data` attribute to control whether query responses include counts. Options are NoMetaData (default), MetaDataOnly (count only), and MetaDataAndResponseData (count plus objects). | |
| ref_number | No | `ref_number` is a user-managed transaction reference (for example, a check number). It can be edited and is not guaranteed to be globally unique. Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`item_filter`, `max_returned`, `modified_date_range_filter`, `pending_status`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices. | |
| 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`. | |
| item_filter | No | Filters according to the item name or ID. You can use an ItemQuery request to get information about all the items that are set up in the QuickBooks file. Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`item_filter`, `max_returned`, `modified_date_range_filter`, `pending_status`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices. | |
| max_returned | No | Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `meta_data` query attribute.) The page size, with `iterator=true`. Sent without `iterator`, or with `iterator=false`, it's a cap instead: at most this many records come back, in one answer, and QuickBooks doesn't say whether more matched. Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`item_filter`, `max_returned`, `modified_date_range_filter`, `pending_status`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices. | |
| include_qbxml | No | Also return the qbXML this compiles to, for debugging. Not part of the v2 request. | |
| pending_status | No | Specifies whether the transaction is pending (posted) or not. Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`item_filter`, `max_returned`, `modified_date_range_filter`, `pending_status`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices. | |
| ref_number_filter | No | Filters by `ref_number` range. Numeric-only bounds are compared numerically; otherwise comparison is lexicographic. Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`item_filter`, `max_returned`, `modified_date_range_filter`, `pending_status`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices. | |
| include_ret_element | No | ||
| txn_date_range_filter | No | Filters according to the original transaction dates. Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`item_filter`, `max_returned`, `modified_date_range_filter`, `pending_status`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices. | |
| ref_number_range_filter | No | Filters by `ref_number` range. Numeric-only bounds are compared numerically; otherwise comparison is lexicographic. Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`item_filter`, `max_returned`, `modified_date_range_filter`, `pending_status`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices. | |
| ref_number_case_sensitive | No | Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`item_filter`, `max_returned`, `modified_date_range_filter`, `pending_status`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices. | |
| modified_date_range_filter | No | Filters according to the dates when transactions were last modified. Choose at most one of: `txn_id`, or `ref_number`, or `ref_number_case_sensitive`, or the set (`item_filter`, `max_returned`, `modified_date_range_filter`, `pending_status`, `ref_number_filter`, `ref_number_range_filter`, `txn_date_range_filter`). Members of a set combine with each other, not with the other choices. | |
| include_component_line_items | No | Specify “true” if component line items for each returned transaction are to be included in the returned data. Specify “false” if the line items aren’t be returned. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Replace {connection_id} with the customer's connection. | |
| qbxml | No | The qbXML it compiles to. Only with include_qbxml. | |
| query | Yes | The query parameters: the arguments you passed. | |
| 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). |