Block Transactions

A block transaction allows the user to group a number of requests within a transaction and send them as a single unit of data. Requests are executed when the whole unit has been sent.

The data unit consists of the block transaction tags, with a number of requests contained within the tags.

It is possible to select if the result to each request is included in the response, by use of the resonly attribute. The selection, even the default when not included, is applied to every request within the block transaction. If an individual request sets the resonly attribute, the attribute is overridden with the value from the block transaction.

The following requests are not permitted within a block transaction, and will result in a INV_REQ_IN_BLOCK_TX error being returned: