Find a deposit

Looks for a specific on-chain transaction among your own addresses and records it if it’s really there but was never picked up. A notification can be lost in a way our own retry cron can’t see: if a deposit was never recorded in the first place, there’s no row for anything to re-drive. This gives you a way to resolve that yourself instead of waiting on a notification that isn’t coming. It only searches addresses on your own account, so it can’t be used to look up anyone else’s transaction.

Endpoint

POST https://merchant.minisend.xyz/api/v1/deposits/find

Authorization: Bearer wsk_live_your_key_here

Requires wallets:write, not a read scope — a successful search books a deposit row and can fire a wallet.deposit.received webhook, so it needs write access even though it looks like a lookup.

Body

string

required

The on-chain transaction hash to look for.

Example

curl -X POST https://merchant.minisend.xyz/api/v1/deposits/find \
  -H "Authorization: Bearer wsk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"tx_hash": "0x55a572efe1720250e442f38741477a4fc3f7f152e5cd208cc52f8222a1c2a13b"}'

Response (200)

Found and newly recorded:

{ "found": true, "recorded": true, "deposit": { "id": "7b2e1a3f-...", "...": "..." } }

Found, but you already had it (no new webhook is fired):

{ "found": true, "recorded": false, "deposit": { "id": "7b2e1a3f-...", "...": "..." } }

deposit is the same shape as get a wallet’s deposits.

Response (404)

{
  "found": false,
  "message": "No deposit with that transaction was found on your addresses. It may still be confirming, or it may have been sent somewhere else."
}

Errors

Status	Meaning
`400`	`tx_hash` isn’t a valid transaction hash
`401`	Missing or invalid API key
`404`	Not found on any of your addresses
`503`	Could not search right now. Retry

Overview

Endpoints

Off-ramp endpoints

Onramp endpoints

Wallet API endpoints

Find a deposit

Endpoint

Body

Example

Response (200)

Response (404)

Errors

​Endpoint

​Body

​Example

​Response (200)

​Response (404)

​Errors

Endpoint

Body

Example

Response (200)

Response (404)

Errors