Account transactions API sending wrong type for "receive" transaction. It is marking "receive" as "send"

Sign in With Coinbase
1

Account transactions API “GET https://api.coinbase.com/v2/accounts/:account_id/transactions” sending wrong type for “receive” transaction. It is marking “receive” as “send”. Here is the detail payload. Unfortunately this is turning into major blocker for our app development as we can’t rely on the transaction type served by the API. Is it possible to get this fixed ? Thank you!! Detail transaction payload below. This is actually a “receive” and not a “send”. {
“id”: “0b66ee45-6543-563e-a38d-e6e02a9573c2”,
“type”: “send”,
“status”: “completed”,
“amount”: {
“amount”: “0.00299157”,
“currency”: “ETH”
},
“native_amount”: {
“amount”: “5.01”,
“currency”: “USD”
},
“description”: null,
“created_at”: “2022-06-10T21:45:53Z”,
“updated_at”: “2022-06-10T22:10:22Z”,
“resource”: “transaction”,
“resource_path”: “/v2/accounts/4fdd534a-244a-5530-b5a5-b7771bf54ab1/transactions/0b66ee45-6543-563e-a38d-e6e02a9573c2”,
“instant_exchange”: false,
“network”: {
“status”: “confirmed”,
“status_description”: null,
“hash”: “ec74df557839efc04cc313d2a0d8a6f7ffc83aeb674db9e4c5652f29058b2896”,
“transaction_url”: “Ethereum Transaction Hash (Txhash) Details | Etherscan”
},
“from”: {
“resource”: “ethereum_network”,
“currency”: “ETH”
},
“details”: {
“title”: “Received Ethereum”,
“subtitle”: “From Ethereum address”,
“header”: “Received 0.00299157 ETH ($5.01)”,
“health”: “positive”
},
“hide_native_amount”: false
}

2

Hey @mahesh! Thank you for using Coinbase APIs. Apologies for the delayed response. We appreciate you sharing this with us. We have taken this as a feedback to update. Our team is aware of this and is working on it to correct. For now we are unable to provide an ETA for this. But we will make sure this gets implemented. Hope this helps. Please keep sharing such valuable feedbacks. Do let us know in case you have any more questions or concerns. Thank you and have a nice day!

3

Do we have any update on this? It’s been nearly two months since this post, and I still see this issue within my own data. I am able to manually sort types, but this is a pain for active development.