An address's transactions (page 1, or filtered)
Ten per page: unconfirmed first, then newest first. With any history filter, the filtered form: the same rows filtered by block, time and direction, paged by cursor, as JSON or CSV.
Request
- Base URL: https://sochain.com/api/v3
- URL: https://sochain.com/api/v3/transactions/{network}/{address}
- Auth: one of:
- none
- API key in header API-KEY
- API key in query parameter api_key
Path parameters
Network code (any case).
An address (letters and digits).
Query parameters
History filter: from this block on (inclusive).
History filter: up to this block (inclusive).
History filter: from this time on. Unix seconds, a UTC date (from its first second) or an RFC 3339 timestamp.
History filter: up to this time. Unix seconds, a UTC date (to its last second) or an RFC 3339 timestamp. Times map to the blocks they cover, so back-to-back ranges neither overlap nor leave a gap.
History filter: in (the balance went up), out (it went down) or both. By the net amount: a payment out with change back counts once, as out.
History filter: pending transactions. Default include, or exclude when the range has an end (to_height or to_time), which can't be combined with include or only.
Rows per page of the filtered form: 1–100 (default 10); with format=csv 1–500 (default 500).
next_cursor from the previous page of the filtered form. It carries the filters, so it can be sent on its own.
json (default) or csv. CSV has one row per transaction (time_utc, block, txid, direction, received, sent, net, price_usd, net_usd); the next page's URL is in the Link header.
Prices in this currency instead of US dollars (any case). Not a filter: on the paged endpoints it keeps the form you'd get without it.
Response
Success.
Example response
{
"data": {
"transactions": [
{
"value_sent": "0.00024300",
"value_received": "0.00024300",
"balance_change": "0.00024300",
"price": {
"value": "0.00024300"
}
}
]
}
}Changes
No recorded changes to this operation across all 1 revision of this API.