Call this endpoint with an account address and a block range (startBlock/endBlock) or a timestamp range (startTimestamp/endTimestamp).

• If no job exists for the given parameters, a new background job will be started to start fetching transactions, and the API will return a 425 (Too Early) with progress information.
• If a job is already running but not yet complete, the API will return a 425 (Too Early) with progress information.
• Once the job finishes, subsequent calls will return a 200 (OK) with paginated transaction data (including standard pagination via nextPageUrl).

To consume results:

1. Call this endpoint and check for HTTP 200 or HTTP 425.
2. If you receive HTTP 425, retry periodically until you receive a 200. Alternatively, if you provided a webhookUrl, you will automatically receive a webhook notification when the job finishes processing.
3. When a 200 is returned, fetch the transactions in the response (which will default to the first 100 transactions) and then call nextPageUrl (if provided) to fetch the remaining pages.

You must supply either both startBlock and endBlock or both startTimestamp and endTimestamp, but not a mix of block and timestamp parameters.

Optionally, you can provide a txLimit parameter to limit the total number of transactions processed. If not provided, all transactions in the specified range will be fetched. By default, the job will fetch transactions starting from the latest block in the range. You can change this to fetch from the start by setting fetchFromBeginning to true.

Optional flags provided in the options parameter let you classify transactions from a different address perspective, exclude spam transactions, include pricing data for tokens, or run balance reconciliation checks. Supported options are:

• prices: enrich txs with token price data when available.
• reconcile: automatically run a balance reconciliation check after processing.
• excludeSpam: exclude transactions flagged as spam.

Additionally, if format is v5, you can provide any of the options supported by /evm/{chain}/{format}/tx/{txHash} endpoint:

• allTransfers: include all additional token/native/internal transfers in addition to perspective-based classification
• internals: include internal transactions details
• traces: include low-level EVM traces
• rawTx: include raw transaction payload
• eventLogs: include decoded event logs
• viewAsTransactionSender: force classification from the transaction sender's perspective