Transfers

Get Crypto Transaction

Returns details about a crypto transaction (incoming or outgoing) for the specified account by transaction ID, including the status of an outgoing crypto transfer after it has been initiated, and the sending address for an incoming deposit.

get/accounts/{account_id}/crypto/{transaction_id}

Request

Base URL
https://api.meow.com/v1
Auth
API key in header x-api-key
TypeScript
https://skmtc.dev/meow/apis/meow-api/docs/accounts/:account_id/crypto/:transaction_id/get.ts
A function with typed inputs. Its response is checked against the schema.

Path parameters

account_idstring required

The ID of the account.

string required

string uuid required

Headers

x-entity-idstring uuid

Optional entity_id to scope requests to a specific entity.

Response

Successful Response

amountstring required

Size of the transaction, in USD. Always positive, in both directions.

direction'inbound' | 'outbound' required

destination_addressstring required

On-chain address the funds were sent to.

destination_tx_hashstring nullable

On-chain hash of the transfer we sent. Set on outbound transactions once they settle.

destination_address_nicknamestring nullable

Nickname of the contact that owns the destination address. null when the address is not attached to a contact, which is the usual case for inbound deposits.

source_addressstring nullable

On-chain address the funds were sent from. Set on inbound deposits, so you can match a deposit to whoever sent it.

source_tx_hashstring nullable

On-chain hash of the deposit. Set on inbound deposits.

metadataobject nullable

The metadata attached when this object was created, unchanged. null when none was attached. Rarely, a .created webhook can be published before the create request finishes committing, and that one event reports null; every later event and every read of the object carries the metadata.

Changes

No recorded changes to this operation across all 1 revision of this API.