@nemtus/symbol-rest-api-client-fetch 1.0.0 → 1.0.2

package/cjs/api/apis/TransactionRoutesApi.d.ts

@@ -10,89 +10,460 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime';
-import type { AnnounceTransactionInfoDTO, Cosignature, Order, TransactionIds, TransactionInfoDTO, TransactionPage, TransactionPayload, TransactionTypeEnum } from '../models/index';
+import { type AnnounceTransactionInfoDTO } from '../models/AnnounceTransactionInfoDTO';
+import { type Cosignature } from '../models/Cosignature';
+import { type Order } from '../models/Order';
+import { type TransactionIds } from '../models/TransactionIds';
+import { type TransactionInfoDTO } from '../models/TransactionInfoDTO';
+import { type TransactionPage } from '../models/TransactionPage';
+import { type TransactionPayload } from '../models/TransactionPayload';
+import { type TransactionTypeEnum } from '../models/TransactionTypeEnum';
 export interface AnnounceCosignatureTransactionRequest {
+    /**
+     *
+     */
     cosignature: Cosignature;
 }
 export interface AnnouncePartialTransactionRequest {
+    /**
+     *
+     */
     transactionPayload: TransactionPayload;
 }
 export interface AnnounceTransactionRequest {
+    /**
+     *
+     */
     transactionPayload: TransactionPayload;
 }
 export interface GetConfirmedTransactionRequest {
+    /**
+     * Transaction hash (64 hexadecimal characters) or node-assigned transaction ID (16 hexadecimal characters).
+     *
+     */
     transactionId: string;
 }
 export interface GetConfirmedTransactionsRequest {
+    /**
+     *
+     */
     transactionIds: TransactionIds;
 }
 export interface GetPartialTransactionRequest {
+    /**
+     * Transaction hash (64 hexadecimal characters) or node-assigned transaction ID (16 hexadecimal characters).
+     *
+     */
     transactionId: string;
 }
 export interface GetPartialTransactionsRequest {
+    /**
+     *
+     */
     transactionIds: TransactionIds;
 }
 export interface GetUnconfirmedTransactionRequest {
+    /**
+     * Transaction hash (64 hexadecimal characters) or node-assigned transaction ID (16 hexadecimal characters).
+     *
+     */
     transactionId: string;
 }
 export interface GetUnconfirmedTransactionsRequest {
+    /**
+     *
+     */
     transactionIds: TransactionIds;
 }
 export interface SearchConfirmedTransactionsRequest {
+    /**
+     * Filter by address (include), in Base32 format.
+     *
+     * The exact meaning depends on the endpoint:
+     * - transaction search: returns transactions where the address appears as the sender, recipient, or cosigner
+     * - account search: matches the account address
+     * - account restriction search: matches the restricted account address
+     * - hash lock and secret lock search: matches the lock owner address
+     *
+     * On transaction search endpoints, this filter cannot be combined with `recipientAddress` and
+     * `signerPublicKey`.
+     *
+     */
     address?: string;
+    /**
+     * Filter transactions by recipient address in Base32 format (include).
+     */
     recipientAddress?: string;
+    /**
+     * Filter transactions by the public key of the signing account (include).
+     */
     signerPublicKey?: string;
+    /**
+     * Filter by height (include).
+     * The exact meaning depends on the endpoint, for example block height for blocks or inclusion height for
+     * confirmed transactions.
+     *
+     */
     height?: string;
+    /**
+     * Only transactions at or above this block height are returned.
+     */
     fromHeight?: string;
+    /**
+     * Only transactions at or below this block height are returned.
+     */
     toHeight?: string;
+    /**
+     * Requires providing the `transferMosaicId` filter.
+     * Only transfer transactions with an amount greater than or equal to this value for the specified mosaic ID are returned.
+     *
+     */
     fromTransferAmount?: string;
+    /**
+     * Requires providing the `transferMosaicId` filter.
+     * Only transfer transactions with an amount less than or equal to this value for the specified mosaic ID are returned.
+     *
+     */
     toTransferAmount?: string;
+    /**
+     * Filter by transaction type (include).
+     * To match multiple transaction types, add more query parameters like: `type=16974&type=16718`.
+     *
+     */
     type?: Array<TransactionTypeEnum>;
+    /**
+     * When `true`, the search also includes transactions embedded inside aggregate transactions.
+     * Otherwise, only top-level transactions are returned.
+     *
+     * Results are **flattened**. Embedded transactions are returned as separate entries in the same
+     * `data` array as top-level transactions, not nested under their parent aggregate transaction.
+     * Sorting, filtering, and pagination are therefore applied to one combined result set containing
+     * both top-level and embedded transaction records.
+     *
+     * In the database, embedded transactions are stored as separate documents linked to their
+     * parent aggregate by `meta.aggregateId` and `meta.aggregateHash`. When `embedded=false`, the
+     * search excludes documents with `meta.aggregateId`. When `embedded=true`, those documents are
+     * included in the page result alongside regular transactions. In REST responses, embedded entries
+     * are identified by `meta.aggregateId`, `meta.aggregateHash`, and their inner `meta.index`;
+     * unlike top-level transactions, they do not carry their own `meta.hash`.
+     *
+     * **Note:** This field does not work as expected with the `address` filter. That filter matches the
+     * internal `meta.addresses` field used on top-level transaction documents, while embedded
+     * transaction documents do not carry that field. As a result, embedded transactions involving the
+     * specified address will not be returned even when `embedded=true`. Filters such as
+     * `recipientAddress` and `signerPublicKey` do not have this limitation.
+     *
+     */
     embedded?: boolean;
+    /**
+     * Filter transfer transactions by the mosaic ID in the transfer payload (include).
+     */
     transferMosaicId?: string;
+    /**
+     * Select the number of entries to return per page.
+     * Values outside the allowed range are clamped to the schema minimum or maximum.
+     *
+     */
     pageSize?: number;
+    /**
+     * Page number for numbered pagination (1-based).
+     *
+     * Numbered and cursor pagination can be combined, but this is not recommended because the semantics
+     * are harder to reason about. For cursor-style flows, keep `pageNumber=1` and advance pages by
+     * updating only `offset`. For numbered pagination flows, omit `offset` and advance pages by
+     * incrementing `pageNumber`.
+     *
+     */
     pageNumber?: number;
+    /**
+     * Cursor for pagination. Provide the value of the sort field (`orderBy`) from the
+     * last entry of the previous page. **The offset type must match `orderBy`:**
+     * - `orderBy=id`: use the entry's `id` (ObjectId, 24-char hex).
+     * - `orderBy=height`: use the block height (string, e.g. `"17592"`).
+     * - `orderBy=balance`: use the mosaic balance amount (string, e.g. `"1000000"`).
+     *
+     * Allowed `orderBy` values depend on the endpoint. If `orderBy` is omitted, `id` is used by default.
+     *
+     * Set `offset` to the sort-field value of the last entry from the previous page. Across pages,
+     * this value decreases with `order=desc` and increases with `order=asc`.
+     *
+     * Numbered and cursor pagination can be combined, but this is not recommended because the semantics
+     * are harder to reason about. For cursor-style flows, keep `pageNumber=1` and advance pages by
+     * updating only `offset`. For numbered pagination flows, omit `offset` and advance pages by
+     * incrementing `pageNumber`.
+     *
+     */
     offset?: string;
+    /**
+     * Sort responses in ascending or descending order based on the collection property set on the param `orderBy`.
+     * If the request does not specify `orderBy`, REST returns the collection ordered by id.
+     * The default sort direction depends on the endpoint implementation.
+     *
+     */
     order?: Order;
 }
 export interface SearchPartialTransactionsRequest {
+    /**
+     * Filter by address (include), in Base32 format.
+     *
+     * The exact meaning depends on the endpoint:
+     * - transaction search: returns transactions where the address appears as the sender, recipient, or cosigner
+     * - account search: matches the account address
+     * - account restriction search: matches the restricted account address
+     * - hash lock and secret lock search: matches the lock owner address
+     *
+     * On transaction search endpoints, this filter cannot be combined with `recipientAddress` and
+     * `signerPublicKey`.
+     *
+     */
     address?: string;
+    /**
+     * Filter transactions by recipient address in Base32 format (include).
+     */
     recipientAddress?: string;
+    /**
+     * Filter transactions by the public key of the signing account (include).
+     */
     signerPublicKey?: string;
+    /**
+     * Filter by height (include).
+     * The exact meaning depends on the endpoint, for example block height for blocks or inclusion height for
+     * confirmed transactions.
+     *
+     */
     height?: string;
+    /**
+     * Only transactions at or above this block height are returned.
+     */
     fromHeight?: string;
+    /**
+     * Only transactions at or below this block height are returned.
+     */
     toHeight?: string;
+    /**
+     * Requires providing the `transferMosaicId` filter.
+     * Only transfer transactions with an amount greater than or equal to this value for the specified mosaic ID are returned.
+     *
+     */
     fromTransferAmount?: string;
+    /**
+     * Requires providing the `transferMosaicId` filter.
+     * Only transfer transactions with an amount less than or equal to this value for the specified mosaic ID are returned.
+     *
+     */
     toTransferAmount?: string;
+    /**
+     * Filter by transaction type (include).
+     * To match multiple transaction types, add more query parameters like: `type=16974&type=16718`.
+     *
+     */
     type?: Array<TransactionTypeEnum>;
+    /**
+     * When `true`, the search also includes transactions embedded inside aggregate transactions.
+     * Otherwise, only top-level transactions are returned.
+     *
+     * Results are **flattened**. Embedded transactions are returned as separate entries in the same
+     * `data` array as top-level transactions, not nested under their parent aggregate transaction.
+     * Sorting, filtering, and pagination are therefore applied to one combined result set containing
+     * both top-level and embedded transaction records.
+     *
+     * In the database, embedded transactions are stored as separate documents linked to their
+     * parent aggregate by `meta.aggregateId` and `meta.aggregateHash`. When `embedded=false`, the
+     * search excludes documents with `meta.aggregateId`. When `embedded=true`, those documents are
+     * included in the page result alongside regular transactions. In REST responses, embedded entries
+     * are identified by `meta.aggregateId`, `meta.aggregateHash`, and their inner `meta.index`;
+     * unlike top-level transactions, they do not carry their own `meta.hash`.
+     *
+     * **Note:** This field does not work as expected with the `address` filter. That filter matches the
+     * internal `meta.addresses` field used on top-level transaction documents, while embedded
+     * transaction documents do not carry that field. As a result, embedded transactions involving the
+     * specified address will not be returned even when `embedded=true`. Filters such as
+     * `recipientAddress` and `signerPublicKey` do not have this limitation.
+     *
+     */
     embedded?: boolean;
+    /**
+     * Filter transfer transactions by the mosaic ID in the transfer payload (include).
+     */
     transferMosaicId?: string;
+    /**
+     * Select the number of entries to return per page.
+     * Values outside the allowed range are clamped to the schema minimum or maximum.
+     *
+     */
     pageSize?: number;
+    /**
+     * Page number for numbered pagination (1-based).
+     *
+     * Numbered and cursor pagination can be combined, but this is not recommended because the semantics
+     * are harder to reason about. For cursor-style flows, keep `pageNumber=1` and advance pages by
+     * updating only `offset`. For numbered pagination flows, omit `offset` and advance pages by
+     * incrementing `pageNumber`.
+     *
+     */
     pageNumber?: number;
+    /**
+     * Cursor for pagination. Provide the value of the sort field (`orderBy`) from the
+     * last entry of the previous page. **The offset type must match `orderBy`:**
+     * - `orderBy=id`: use the entry's `id` (ObjectId, 24-char hex).
+     * - `orderBy=height`: use the block height (string, e.g. `"17592"`).
+     * - `orderBy=balance`: use the mosaic balance amount (string, e.g. `"1000000"`).
+     *
+     * Allowed `orderBy` values depend on the endpoint. If `orderBy` is omitted, `id` is used by default.
+     *
+     * Set `offset` to the sort-field value of the last entry from the previous page. Across pages,
+     * this value decreases with `order=desc` and increases with `order=asc`.
+     *
+     * Numbered and cursor pagination can be combined, but this is not recommended because the semantics
+     * are harder to reason about. For cursor-style flows, keep `pageNumber=1` and advance pages by
+     * updating only `offset`. For numbered pagination flows, omit `offset` and advance pages by
+     * incrementing `pageNumber`.
+     *
+     */
     offset?: string;
+    /**
+     * Sort responses in ascending or descending order based on the collection property set on the param `orderBy`.
+     * If the request does not specify `orderBy`, REST returns the collection ordered by id.
+     * The default sort direction depends on the endpoint implementation.
+     *
+     */
     order?: Order;
 }
 export interface SearchUnconfirmedTransactionsRequest {
+    /**
+     * Filter by address (include), in Base32 format.
+     *
+     * The exact meaning depends on the endpoint:
+     * - transaction search: returns transactions where the address appears as the sender, recipient, or cosigner
+     * - account search: matches the account address
+     * - account restriction search: matches the restricted account address
+     * - hash lock and secret lock search: matches the lock owner address
+     *
+     * On transaction search endpoints, this filter cannot be combined with `recipientAddress` and
+     * `signerPublicKey`.
+     *
+     */
     address?: string;
+    /**
+     * Filter transactions by recipient address in Base32 format (include).
+     */
     recipientAddress?: string;
+    /**
+     * Filter transactions by the public key of the signing account (include).
+     */
     signerPublicKey?: string;
+    /**
+     * Filter by height (include).
+     * The exact meaning depends on the endpoint, for example block height for blocks or inclusion height for
+     * confirmed transactions.
+     *
+     */
     height?: string;
+    /**
+     * Only transactions at or above this block height are returned.
+     */
     fromHeight?: string;
+    /**
+     * Only transactions at or below this block height are returned.
+     */
     toHeight?: string;
+    /**
+     * Requires providing the `transferMosaicId` filter.
+     * Only transfer transactions with an amount greater than or equal to this value for the specified mosaic ID are returned.
+     *
+     */
     fromTransferAmount?: string;
+    /**
+     * Requires providing the `transferMosaicId` filter.
+     * Only transfer transactions with an amount less than or equal to this value for the specified mosaic ID are returned.
+     *
+     */
     toTransferAmount?: string;
+    /**
+     * Filter by transaction type (include).
+     * To match multiple transaction types, add more query parameters like: `type=16974&type=16718`.
+     *
+     */
     type?: Array<TransactionTypeEnum>;
+    /**
+     * When `true`, the search also includes transactions embedded inside aggregate transactions.
+     * Otherwise, only top-level transactions are returned.
+     *
+     * Results are **flattened**. Embedded transactions are returned as separate entries in the same
+     * `data` array as top-level transactions, not nested under their parent aggregate transaction.
+     * Sorting, filtering, and pagination are therefore applied to one combined result set containing
+     * both top-level and embedded transaction records.
+     *
+     * In the database, embedded transactions are stored as separate documents linked to their
+     * parent aggregate by `meta.aggregateId` and `meta.aggregateHash`. When `embedded=false`, the
+     * search excludes documents with `meta.aggregateId`. When `embedded=true`, those documents are
+     * included in the page result alongside regular transactions. In REST responses, embedded entries
+     * are identified by `meta.aggregateId`, `meta.aggregateHash`, and their inner `meta.index`;
+     * unlike top-level transactions, they do not carry their own `meta.hash`.
+     *
+     * **Note:** This field does not work as expected with the `address` filter. That filter matches the
+     * internal `meta.addresses` field used on top-level transaction documents, while embedded
+     * transaction documents do not carry that field. As a result, embedded transactions involving the
+     * specified address will not be returned even when `embedded=true`. Filters such as
+     * `recipientAddress` and `signerPublicKey` do not have this limitation.
+     *
+     */
     embedded?: boolean;
+    /**
+     * Filter transfer transactions by the mosaic ID in the transfer payload (include).
+     */
     transferMosaicId?: string;
+    /**
+     * Select the number of entries to return per page.
+     * Values outside the allowed range are clamped to the schema minimum or maximum.
+     *
+     */
     pageSize?: number;
+    /**
+     * Page number for numbered pagination (1-based).
+     *
+     * Numbered and cursor pagination can be combined, but this is not recommended because the semantics
+     * are harder to reason about. For cursor-style flows, keep `pageNumber=1` and advance pages by
+     * updating only `offset`. For numbered pagination flows, omit `offset` and advance pages by
+     * incrementing `pageNumber`.
+     *
+     */
     pageNumber?: number;
+    /**
+     * Cursor for pagination. Provide the value of the sort field (`orderBy`) from the
+     * last entry of the previous page. **The offset type must match `orderBy`:**
+     * - `orderBy=id`: use the entry's `id` (ObjectId, 24-char hex).
+     * - `orderBy=height`: use the block height (string, e.g. `"17592"`).
+     * - `orderBy=balance`: use the mosaic balance amount (string, e.g. `"1000000"`).
+     *
+     * Allowed `orderBy` values depend on the endpoint. If `orderBy` is omitted, `id` is used by default.
+     *
+     * Set `offset` to the sort-field value of the last entry from the previous page. Across pages,
+     * this value decreases with `order=desc` and increases with `order=asc`.
+     *
+     * Numbered and cursor pagination can be combined, but this is not recommended because the semantics
+     * are harder to reason about. For cursor-style flows, keep `pageNumber=1` and advance pages by
+     * updating only `offset`. For numbered pagination flows, omit `offset` and advance pages by
+     * incrementing `pageNumber`.
+     *
+     */
     offset?: string;
+    /**
+     * Sort responses in ascending or descending order based on the collection property set on the param `orderBy`.
+     * If the request does not specify `orderBy`, REST returns the collection ordered by id.
+     * The default sort direction depends on the endpoint implementation.
+     *
+     */
     order?: Order;
 }
 /**
  *
  */
 export declare class TransactionRoutesApi extends runtime.BaseAPI {
+    /**
+     * Creates request options for announceCosignatureTransaction without sending the request
+     */
+    announceCosignatureTransactionRequestOpts(requestParameters: AnnounceCosignatureTransactionRequest): Promise<runtime.RequestOpts>;
     /**
      * Broadcasts a detached cosignature for an aggregate bonded transaction to the network through this node.  The request must contain the detached cosignature fields: cosignature version, signer public key, cosignature signature, and the parent aggregate transaction hash. Detached cosignatures are normally created client-side with a [Symbol SDK](https://docs.symbol.dev/sdk.html) and then announced with this endpoint.  Acceptance by this node does not mean the parent aggregate bonded transaction is already confirmed on-chain. The cosignature still needs to be propagated and processed by the network.  To verify the effect of the cosignature, query the **parent aggregate bonded transaction**, for example with [`GET /transactionStatus/{hash}`](/transactionStatus/{hash}) using the parent aggregate transaction hash. Transaction status availability is not guaranteed indefinitely: failed statuses are stored in a capped collection and may be evicted as new entries arrive.
      * Announce a cosignature transaction
@@ -103,6 +474,10 @@ export declare class TransactionRoutesApi extends runtime.BaseAPI {
      * Announce a cosignature transaction
      */
     announceCosignatureTransaction(requestParameters: AnnounceCosignatureTransactionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AnnounceTransactionInfoDTO>;
+    /**
+     * Creates request options for announcePartialTransaction without sending the request
+     */
+    announcePartialTransactionRequestOpts(requestParameters: AnnouncePartialTransactionRequest): Promise<runtime.RequestOpts>;
     /**
      * Broadcasts a signed aggregate bonded transaction to the network through this node.  The request must contain the serialized aggregate bonded transaction payload in hexadecimal form. Transactions are normally created and signed client-side with a [Symbol SDK](https://docs.symbol.dev/sdk.html) and then announced with this endpoint.  Acceptance by this node does not mean the transaction is already part of the blockchain. The transaction still needs to be validated and confirmed by the network.  To verify the final result, query `GET /transactionStatus/{hash}` on the same node that received the announce request. If that node drops the transaction before propagation, other nodes may not know the transaction at all and can return `404` for the same hash. Transaction status availability is not guaranteed indefinitely: failed statuses are stored in a capped collection and may be evicted as new entries arrive.
      * Announce an aggregate bonded transaction
@@ -113,6 +488,10 @@ export declare class TransactionRoutesApi extends runtime.BaseAPI {
      * Announce an aggregate bonded transaction
      */
     announcePartialTransaction(requestParameters: AnnouncePartialTransactionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AnnounceTransactionInfoDTO>;
+    /**
+     * Creates request options for announceTransaction without sending the request
+     */
+    announceTransactionRequestOpts(requestParameters: AnnounceTransactionRequest): Promise<runtime.RequestOpts>;
     /**
      * Broadcasts a signed transaction to the network through this node.  The request must contain the serialized transaction payload in hexadecimal form. Transactions are normally created and signed client-side with a [Symbol SDK](https://docs.symbol.dev/sdk.html) and then announced with this endpoint.  The [catbuffer library](https://github.com/symbol/symbol/tree/main/catbuffer) defines the binary serialization format used by Symbol entities.  Acceptance by this node does not mean the transaction is already part of the blockchain. The transaction still needs to be validated and confirmed by the network.  To verify the final result, query `GET /transactionStatus/{hash}` on the same node that received the announce request. If that node drops the transaction before propagation, other nodes may not know the transaction at all and can return `404` for the same hash. Transaction status availability is not guaranteed indefinitely: failed statuses are stored in a capped collection and may be evicted as new entries arrive.
      * Announce a new transaction
@@ -123,6 +502,10 @@ export declare class TransactionRoutesApi extends runtime.BaseAPI {
      * Announce a new transaction
      */
     announceTransaction(requestParameters: AnnounceTransactionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AnnounceTransactionInfoDTO>;
+    /**
+     * Creates request options for getConfirmedTransaction without sending the request
+     */
+    getConfirmedTransactionRequestOpts(requestParameters: GetConfirmedTransactionRequest): Promise<runtime.RequestOpts>;
     /**
      * Returns confirmed transaction information given a transaction ID assigned by the node or transaction hash.  Use this endpoint when you need on-chain transaction data (the transaction is already included in a block). Use `getUnconfirmedTransaction` while the transaction is still in a node\'s unconfirmed pool, and use `getPartialTransaction` for aggregate bonded transactions waiting for cosignatures.
      * Get confirmed transaction information
@@ -133,6 +516,10 @@ export declare class TransactionRoutesApi extends runtime.BaseAPI {
      * Get confirmed transaction information
      */
     getConfirmedTransaction(requestParameters: GetConfirmedTransactionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<TransactionInfoDTO>;
+    /**
+     * Creates request options for getConfirmedTransactions without sending the request
+     */
+    getConfirmedTransactionsRequestOpts(requestParameters: GetConfirmedTransactionsRequest): Promise<runtime.RequestOpts>;
     /**
      * Returns confirmed transactions for the list of identifiers in the request body. Each request item can be either a transaction ID assigned by the node or a transaction hash. Both values are returned by transaction retrieval and search endpoints, for example `GET /transactions/confirmed` and `GET /transactions/confirmed/{transactionId}`.  Use this endpoint when you need on-chain data for multiple transactions in one call. Use `getUnconfirmedTransactions` for transactions still pending in a node pool, and use `getPartialTransactions` for aggregate bonded transactions waiting for cosignatures.
      * Get confirmed transactions information
@@ -143,6 +530,10 @@ export declare class TransactionRoutesApi extends runtime.BaseAPI {
      * Get confirmed transactions information
      */
     getConfirmedTransactions(requestParameters: GetConfirmedTransactionsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Array<TransactionInfoDTO>>;
+    /**
+     * Creates request options for getPartialTransaction without sending the request
+     */
+    getPartialTransactionRequestOpts(requestParameters: GetPartialTransactionRequest): Promise<runtime.RequestOpts>;
     /**
      * Returns one partial transaction identified by the path value. Partial transactions are aggregate bonded transactions waiting for the remaining cosignatures.  The path accepts either the transaction ID assigned by the node or the transaction hash. Both values are returned by transaction retrieval and search endpoints, for example `GET /transactions/partial` and `GET /transactions/partial/{transactionId}`.  Use this endpoint for aggregate bonded transactions before they are fully cosigned. Use `getUnconfirmedTransaction` for non-partial transactions that are in a node\'s unconfirmed pool, and use `getConfirmedTransaction` once the transaction is confirmed on-chain.
      * Get partial transaction information
@@ -153,6 +544,10 @@ export declare class TransactionRoutesApi extends runtime.BaseAPI {
      * Get partial transaction information
      */
     getPartialTransaction(requestParameters: GetPartialTransactionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<TransactionInfoDTO>;
+    /**
+     * Creates request options for getPartialTransactions without sending the request
+     */
+    getPartialTransactionsRequestOpts(requestParameters: GetPartialTransactionsRequest): Promise<runtime.RequestOpts>;
     /**
      * Returns partial transactions for the list of identifiers in the request body. Partial transactions are aggregate bonded transactions waiting for the remaining cosignatures.  Each request item can be either a transaction ID assigned by the node or a transaction hash. Both values are returned by transaction retrieval and search endpoints, for example `GET /transactions/partial` and `GET /transactions/partial/{transactionId}`.  Use this endpoint for aggregate bonded transactions that still wait for required cosignatures. Use `getUnconfirmedTransactions` for non-partial pending transactions accepted by a node but not yet included in a block, and use `getConfirmedTransactions` once transactions are confirmed on-chain.
      * Get information about partial transactions
@@ -163,6 +558,10 @@ export declare class TransactionRoutesApi extends runtime.BaseAPI {
      * Get information about partial transactions
      */
     getPartialTransactions(requestParameters: GetPartialTransactionsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Array<TransactionInfoDTO>>;
+    /**
+     * Creates request options for getUnconfirmedTransaction without sending the request
+     */
+    getUnconfirmedTransactionRequestOpts(requestParameters: GetUnconfirmedTransactionRequest): Promise<runtime.RequestOpts>;
     /**
      * Returns one unconfirmed transaction identified by the path value. An unconfirmed transaction is accepted by a node and pending inclusion in a block.  The path accepts either the transaction ID assigned by the node or the transaction hash. Both values are returned by transaction retrieval and search endpoints, for example `GET /transactions/unconfirmed` and `GET /transactions/unconfirmed/{transactionId}`.  Use this endpoint while a transaction is accepted by a node but not yet included in a block. Use `getConfirmedTransaction` once it is confirmed on-chain, and use `getPartialTransaction` for aggregate bonded transactions waiting for cosignatures.
      * Get unconfirmed transaction information
@@ -173,6 +572,10 @@ export declare class TransactionRoutesApi extends runtime.BaseAPI {
      * Get unconfirmed transaction information
      */
     getUnconfirmedTransaction(requestParameters: GetUnconfirmedTransactionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<TransactionInfoDTO>;
+    /**
+     * Creates request options for getUnconfirmedTransactions without sending the request
+     */
+    getUnconfirmedTransactionsRequestOpts(requestParameters: GetUnconfirmedTransactionsRequest): Promise<runtime.RequestOpts>;
     /**
      * Returns unconfirmed transactions for the list of identifiers in the request body. Unconfirmed transactions are accepted by a node and pending inclusion in a block.  Each request item can be either a transaction ID assigned by the node or a transaction hash. Both values are returned by transaction retrieval and search endpoints, for example `GET /transactions/unconfirmed` and `GET /transactions/unconfirmed/{transactionId}`.  Use this endpoint when checking multiple transactions that are accepted by a node but not yet included in a block. Use `getConfirmedTransactions` for on-chain transactions, and use `getPartialTransactions` for aggregate bonded transactions waiting for cosignatures.
      * Get information about unconfirmed transactions
@@ -183,6 +586,10 @@ export declare class TransactionRoutesApi extends runtime.BaseAPI {
      * Get information about unconfirmed transactions
      */
     getUnconfirmedTransactions(requestParameters: GetUnconfirmedTransactionsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Array<TransactionInfoDTO>>;
+    /**
+     * Creates request options for searchConfirmedTransactions without sending the request
+     */
+    searchConfirmedTransactionsRequestOpts(requestParameters: SearchConfirmedTransactionsRequest): Promise<runtime.RequestOpts>;
     /**
      * Returns a paginated list of confirmed transactions matching the supplied filters.  Use this endpoint when you need on-chain transactions only (already included in blocks). Use `searchUnconfirmedTransactions` for transactions that are still pending in a node pool, and use `searchPartialTransactions` for aggregate bonded transactions waiting for cosignatures.  If a transaction was announced with an alias rather than an address, the address considered during filtering is the one resolved from that alias at confirmation time.  For cursor-style pagination on this endpoint, set `offset` to the `id` of the last transaction from the previous page. For general pagination strategy guidance, see the `offset` and `pageNumber` query parameter descriptions.
      * Search confirmed transactions
@@ -193,6 +600,10 @@ export declare class TransactionRoutesApi extends runtime.BaseAPI {
      * Search confirmed transactions
      */
     searchConfirmedTransactions(requestParameters?: SearchConfirmedTransactionsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<TransactionPage>;
+    /**
+     * Creates request options for searchPartialTransactions without sending the request
+     */
+    searchPartialTransactionsRequestOpts(requestParameters: SearchPartialTransactionsRequest): Promise<runtime.RequestOpts>;
     /**
      * Returns a paginated list of partial transactions matching the supplied filters.  Use this endpoint for aggregate bonded transactions that still wait for required cosignatures. Use `searchUnconfirmedTransactions` for non-partial pending transactions, and use `searchConfirmedTransactions` once transactions are confirmed on-chain.  For cursor-style pagination on this endpoint, set `offset` to the `id` of the last transaction from the previous page. For general pagination strategy guidance, see the `offset` and `pageNumber` query parameter descriptions.
      * Search partial transactions
@@ -203,6 +614,10 @@ export declare class TransactionRoutesApi extends runtime.BaseAPI {
      * Search partial transactions
      */
     searchPartialTransactions(requestParameters?: SearchPartialTransactionsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<TransactionPage>;
+    /**
+     * Creates request options for searchUnconfirmedTransactions without sending the request
+     */
+    searchUnconfirmedTransactionsRequestOpts(requestParameters: SearchUnconfirmedTransactionsRequest): Promise<runtime.RequestOpts>;
     /**
      * Returns a paginated list of unconfirmed transactions matching the supplied filters.  Use this endpoint for transactions accepted by a node but not yet included in a block. Use `searchConfirmedTransactions` for on-chain transactions, and use `searchPartialTransactions` for aggregate bonded transactions waiting for cosignatures.  For cursor-style pagination on this endpoint, set `offset` to the `id` of the last transaction from the previous page. For general pagination strategy guidance, see the `offset` and `pageNumber` query parameter descriptions.
      * Search unconfirmed transactions