1Shot API icon

1Shot API

Interact with EVM blockchains via 1Shot API

Actions27

Transaction → List Transactions

AI-generated

Overview

This node operation lists transactions from the 1Shot API based on various filter criteria. It is useful for retrieving transaction data filtered by status, wallet ID, contract method ID, API credential ID, user ID, memo text, creation time range, pagination, and blockchain chain ID. Practical examples include fetching all completed transactions for a specific wallet within a certain time frame or retrieving transactions related to a particular contract method.

Use Case Examples

  1. List all completed transactions for a given wallet ID between two timestamps.
  2. Retrieve transactions filtered by status 'Pending' and a specific user ID.
  3. Get paginated transaction data with a page size of 50 for a specific blockchain chain.

Properties

Name Meaning
Status Filter transactions by their status such as Pending, Submitted, Completed, Retrying, or Failed.
Wallet ID Filter transactions by the wallet ID associated with them.
Contract Method ID Filter transactions by the contract method ID involved.
API Credential ID Filter transactions by the API credential ID used.
User ID Filter transactions by the user ID who initiated the transaction.
Memo Filter transactions by matching memo text.
After Time Filter transactions created after this Unix timestamp.
Before Time Filter transactions created before this Unix timestamp.
Page Number Specify the page number of results to retrieve, starting at 1.
Page Size Specify the number of transactions to retrieve per page.
Chain Name or ID Filter transactions by blockchain chain name or ID.

Output

JSON

  • json - Each item contains a transaction object with details as returned by the 1Shot API.

Dependencies

  • 1Shot API with OAuth2 API key credential

Troubleshooting

  • Ensure the OAuth2 API credential is correctly configured and authorized to access the 1Shot API.
  • Verify that the filter parameters such as timestamps and IDs are valid and correctly formatted.
  • If the node returns an error about unsupported operations, confirm that the resource is set to 'Transaction' and operation to 'List Transactions'.
  • Check API rate limits and use batching options if encountering rate limit errors (HTTP 429).
  • If the node returns empty results, verify that the filter criteria match existing transactions in the 1Shot API.

Links

Discussion