Get Sub-account Activity
This operation allows the client to fetch a specific transaction activity by its ID.
Authorizations
Requires authentication via API key and HMAC signature.
x-api-key: Your API key generated from your Onboard Business dashboard.x-timestamp: Unix epoch timestamp (seconds) used in signature, allowed skew is 30 secondsx-signature: SHA256 HMAC HEX signature calculated overt={x-timestamp}&{requestBody}using your API Secret.
Path Parameters
The unique onboard sub-account ID or reference
The unique transaction activity ID
Response
Activity fetched successfully
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
A single entry in the aggregated account activity feed. The concrete subtype is determined by the activityType discriminator; the type field carries the semantic category for filtering and display.
Details of a cash deposit transaction.
Discriminator; the concrete activity model name, e.g. CashDepositActivity.
Semantic category of a transaction activity feed entry.
CASH_DEPOSIT, CASH_PAYMENT, ACCOUNT_NUMBER_DEPOSIT, CRYPTO_WITHDRAWAL, CRYPTO_DEPOSIT, INTERNAL_TRANSFER, OFFRAMP_DEPOSIT CREDIT, DEBIT Always positive; see direction for credit/debit.
100
"USD"
Status of the transaction, indicating its current state in the processing lifecycle.
- PENDING: The transaction has been created but not yet processed.
- IN_PROGRESS: The transaction is currently being processed.
- FAILED: The transaction processing has failed.
- SUCCESS: The transaction has been successfully processed.
PENDING, IN_PROGRESS, FAILED, SUCCESS The kind of account a transaction activity occurred on.
MAIN, SUB_ACCOUNT, OFFRAMP_ACCOUNT Customer-facing reference of the source transaction.
Set when accountType is SUB_ACCOUNT.
Identifier of the transaction on the ledger account, when available.
Links related activities together, e.g. the two legs of an internal transfer, or an offramp deposit and its refund.