Check Payment Address Logs
Returns all incoming payments, forwarded transactions, and webhook attempts for a payment address created through the /{ticker}/create/ endpoint. Each entry corresponds to a single incoming transaction received on the payment address.
https://api.kingpay.online/{ticker}/logs/ Replace {ticker} with the cryptocurrency/network identifier (e.g. btc, eth, trc20/usdt).
Notices
- This endpoint returns logs only for payment addresses created via the
/{ticker}/create/endpoint. - The exact
callbackURL used during creation must be provided in the query. - The
callbacksarray lists all incoming transactions received on the address. A single address may receive multiple payments. - Each incoming transaction may generate one or more forwarding transactions depending on your split configuration.
- Each callback entry also contains a
logsarray describing all webhook attempts made for that specific incoming transaction.
Path parameters
ticker string • required
Identifies the cryptocurrency and network this request refers to.
btc— Bitcoin mainneteth— Ethereumtrc20/usdt— USDT on TRON TRC-20
Example: https://api.kingpay.online/trc20/usdt/logs/
Query parameters (required)
callback string • required
The callback URL of the payment address. Must match exactly the value originally provided to /{ticker}/create/.
- URL-encoding is recommended (most HTTP clients do this automatically).
- Any extra GET parameters must also be included exactly as sent originally.
Example: https://example.com/ipn/cryptapi?invoice_id=123
Top-level response fields
address_in— payment address created for this callback.address_out— object with forwarding destinations and percentages.callback_url— registered callback URL.status— normally"success".notify_pending— saved legacy option; UTXO confirmation progress is sent regardless of this flag.notify_confirmations— required confirmation count.priority— forwarding fee priority.callbacks— list of incoming payments (see below).
Fields inside callbacks[]
txid_in— incoming transaction hash.forwards[]— array of all forwarding transactions created for this incoming payment.value_coin— amount received from customer.confirmations— saved confirmation count; not a live blockchain query.txid_out— single outgoing hash, ornullwhen there are several or none. Useforwards[]for the full list.value_forwarded_coin— total forwarded amount from the saved webhook, ornullwhen unknown.fee_coinandfee_percent— total service fee for this incoming payment, in payment units and percent.network_fee— separate network-cost deduction in the payment currency; unknown historical values arenull.last_update— last update timestamp (UTC).result—"pending","sent"or"done"(see below).logs— webhook attempts for this incoming transaction.deliveries— delivery states for notifications created after automatic retries were introduced.
Fields inside callbacks[].forwards[]
txid_out— outgoing (forwarding) transaction hash.address_out— destination address.value_forwarded_coin— forwarded amount.
The total service fee is returned only as callbacks[].fee_coin and callbacks[].fee_percent. Forward entries do not repeat the fee. Without a saved association, forwards is an empty array. Unknown per-transfer amounts and destinations are null. Unknown fees remain null, including old UTXO webhooks whose fee represented network costs. A known zero service fee is returned as 0. Forward hashes come from the saved webhook; a destination is null when the webhook does not identify one address for that hash.
Fields inside callbacks[].logs[]
request_url— request URL used when calling your webhook.responses— raw response body.response_status— HTTP status code.next_try— next retry timestamp (if scheduled).payment_status— pending, confirmed, or completed for this callback.confirmed— whether the callback was a "confirmed" notification.uuid,attempt— notification ID and attempt number for new deliveries.created_at,error— attempt time (UTC) and failure reason, if any.
Fields inside callbacks[].deliveries[]
uuid— stable notification identifier, shared by all its retries.status—queued,sending,retry,deliveredorfailed.attempts— number of started attempts, including interrupted attempts.next_try— next scheduled attempt (UTC), ornullwhen none remains.created_at,expires_at— notification creation and the end of its 48-hour delivery window.error— latest error or expiration reason.
An interrupted attempt can have an unknown outcome. It may be retried with the same UUID. Older logs remain available, but have no delivery state and are not automatically resent.
Payment status values (callbacks[].result)
pending— no outgoing transaction is associated by the current logs implementation.sent— outgoing hashes are known, but successful confirmed-webhook delivery is not recorded.done— outgoing hashes are known and a confirmed webhook was delivered.- Check
deliveries[].statusfor webhook acknowledgement.deliveredmeans HTTP 2xx with JSON{"status":"ok"}or legacy text*ok*;failedmeans the 48-hour window has expired.