List Address Transactions
List transactions for a specific on-chain deposit address on a Coinbase Business account. Returns incoming transactions received at the address including amount, status, and network details. Ideal for: monitoring deposits, tracking incoming payments, verifying receipt of funds, payment reconciliation.
Catalog action Integrations coinbase-business
List transactions for a specific on-chain deposit address on a Coinbase Business account. Returns incoming transactions received at the address including amount, status, and network details. Ideal for: monitoring deposits, tracking incoming payments, verifying receipt of funds, payment reconciliation.
At a Glance
| Field | Value |
|---|---|
| Action ID | coinbase-business-list-address-transactions |
| Category | Integrations |
| Connector | coinbase-business |
| Requires gas | No |
| Funds movement | None declared |
| Tags | coinbase, address, transactions, deposit, receive, crypto, finance, read |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
accountId | string | Yes | Account UUID — MUST be a UUID (e.g., 'a9fee464-782f-5ace-b2d3-...'). Do NOT pass a currency code like 'USDC'. Get the UUID by calling coinbase-business-get-account first, then use {{get_account.result.id}}. |
addressId | string | Yes | Coinbase address resource UUID (NOT a blockchain address). Must be a UUID or a {{template}} variable. Get from list-addresses result: {{list_addresses.result.addresses[0].id}}. |
pageToken | string | No | Pagination token for fetching the next page |
pageSize | integer | No | Number of transactions to return per page (default: 25, max: 100) |
apiKeyName | string | No | CDP API Key Name (overrides connector) |
apiKeySecret | string | No | CDP API Key Secret (overrides connector) |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
transactions | array | Yes | List of transactions for this address |
nextPageToken | string | No | Token for fetching the next page |
Examples
json{ "type": "coinbase-business-list-address-transactions", "payload": { "accountId": "example-accountId", "addressId": "example-addressId" }, "children": [], "connector": { "type": "coinbase-business", "id": "conn_coinbase_business" }}
bashcurl -X POST "https://api.b3os.org/v1/actions/coinbase-business-list-address-transactions/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "accountId": "example-accountId", "addressId": "example-addressId" }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.