Get a transaction receipt
After sending a transaction you need its receipt to confirm success, read gas used and pull emitted logs. Use standard eth_getTransactionReceipt or the REST receipt path. Both hit our nodes directly — no infrastructure on your side.
- An API key (sk_live_...) with C1 read access.
- A confirmed transaction hash on eth or tron.
1Fetch the receipt over JSON-RPC
POST eth_getTransactionReceipt to /v1/rpc/eth. This is the unchanged standard method; only the base URL and auth header differ.
curl https://api.1st-node.com/v1/rpc/eth \
-H "Authorization: Bearer sk_live_..." \
-d '{"method":"eth_getTransactionReceipt","params":["0x8f2a...c91b"]}'2Or use the REST receipt endpoint
GET the receipt path if you prefer a plain HTTP call over building an RPC envelope. Both return the same underlying receipt.
curl https://api.1st-node.com/v1/data/eth/tx/0x8f2a...c91b/receipt \ -H "Authorization: Bearer sk_live_..."
3Check status and logs
status is 0x1 on success, 0x0 on revert. gasUsed and logs come with the receipt so you can confirm effects in one read.
> {
> "transactionHash": "0x8f2a...c91b",
> "status": "0x1",
> "gasUsed": "0x5208",
> "blockNumber": "0x12d687",
> "logs": []
> }Sıkça sorulanlar
Why is my receipt null?
The transaction is not yet mined. Poll eth_getTransactionReceipt until it returns a receipt, or watch for the block that includes the hash.
Do I need my own node to poll receipts?
No. Polling runs against our nodes over standard JSON-RPC. You pay per call, so there is no idle server cost between transactions.
Okumaya devam et
Bakiye yükle, anahtarını al, yayına çık.
Self servis. Kripto ya da kartla öde. Krediyle ölçümlenir — ağır ilkel yapılar daha pahalı, basitler ucuz.
API anahtarı al