is there a way to fetch all transactions of all accounts of a user at once?
We have tried account-based transactions API and could fetch the transaction history successfully, but we wanted to fetch user-based transactions. Please advise if any possibility of this.
Thanks for the support. Thank You in advance!
Hello @nydeepak1! Welcome to the forum! Unfortunately, fetching user-based transactions is currently not available via the API. We only have the List Transactions endpoint that will list the transactions of an account (wallets) by account ID.
Moving forward, we will log this as a feature request with our internal teams so we can continue improving our user experience. Most new features and improvements to our products come directly from feedback like yours, so it’s very valuable to us. While we can’t offer any specific timeline for adding features, we are constantly working to build products our customers will love.
If you want to stay up to date on the latest from Coinbase Cloud, you can also bookmark the following webpage and subscribe to email updates at the bottom of the page: https://www.coinbase.com/cloud/discover
We really appreciate you for bringing this up to our attention, thank you! Again, welcome to the community!
Thank You very much for the response
Hi @Lioness,
Thank you very much for the response.
We are fetching transactions through API calls that have a limitation of API rate limits.
To get more data in a short time is there WebSocket available for transactions?
We see that something similar is there for orders in the documentation.
And we see that the API https://api.coinbase.com/v2/transactions isn’t working anymore, is there any new request we need to follow?
please advise.
Thanks in advance
Hi @nydeepak1! With regard to your inquiry about a Websocket for transactions, unfortunately, there is no Websocket available in Sign in with Coinbase. However, you may try setting up the Notifications endpoint in Sign in with Coinbase. Notifications allow you to subscribe to updates for your OAuth application or API key. Notifications are sent as HTTP POST requests (webhooks) to a notification endpoint which you can set in your OAuth application or API key settings. Once you have configured your notification endpoint you’ll receive notifications instantly as events are created for your account. You might use notifications to:
For your other inquiry about the API for Transactions, we have tried testing it in our end and we were able to successfully call the endpoint. Based from our last response where we have recommended the List Transactions endpoint, the URL you have sent has a slight discrepancy with the one in the documentation. The correct URL for calling the List Transactions should be https://api.coinbase.com/v2/accounts/:account_id/transactions. To get the account_id, you may run the List Accounts endpoint to select the account/wallet of your choice.
We would appreciate it if you try our provided HTTP request and see if it works for you. Please do not hesitate to reply on this thread if the issue still persists. Have a great day ahead!
Hi @Faker Thank you very much for the response.
We are trying to set up the webhook for the Notifications through OAuth2.
Unfortunately, we aren’t able to do due to a lack of info.
Could you please help us here if any documentation to setup this up from scratch?
Below is the documentation we followed.
Please let us know if there is any specific documentation we can follow.
Thanks for the support.
Thanks in advance.
Hi @nydeepak1! We understand that you are trying to set up the webhook for the Notifications through OAuth2.
We will log your concern as feedback to update the documentation to have a step-by-step process for setting up the webhook for the Notifications through OAuth2 with our internal teams so we can continue improving our user experience. Most new features and improvements to our products come directly from feedback like yours, so it’s very valuable to us. While we can’t offer any specific timeline for adding features, we are constantly working to build products our customers will love.
Rest assured that we will also get back to you once we have the information as the team is still looking into it.
If you want to stay up to date on the latest from Coinbase Cloud, you can also bookmark the following webpage and subscribe to email updates at the bottom of the page: https://www.coinbase.com/cloud/discover
We appreciate your patience and understanding on this. Please let us know if you have any other questions.
Do you have any documentation currently that we could follow, even if it’s not as perfect? we need something that throws light on the process.
Thanks in advance.
Hi @nydeepak1! Currently, the only documentation available for setting up the Webhook Notifications through OAuth2 is the one found here: Notifications | Coinbase Cloud
We would need to wait for our internal teams to share elaborate steps on how to set up the Notifications endpoint using OAuth2.
We appreciate your patience and understanding.
Thank You very much for the response.
We have created our own API to register for the notification services, as part of testing we have used the user who has authorized the scope mentioned below
scope=wallet:accounts:read,wallet:addresses:read,wallet:buys:read,wallet:deposits:read,wallet:notifications:read,wallet:payment-methods:read,wallet:sells:read,wallet:transactions:read,wallet:user:read,wallet:withdrawals:read
When this user does deposits, we get a notification. But when any withdrawals or market or limit order is placed, we don’t receive notifications.
is there anything specific activity or configuration that needs to be done to get notified on all events? Please advise
Thanks in advance
Hi @nydeepak1! Currently, Notifications will only be triggered if one of the actions mentioned here are completed, so only for withdraws, deposits, buys, sells or if you receive a new on-chain payment on one of your crypto addresses. Additionally, transactions sent off-chain and/or to an email address, for example, won’t generate any notifications.
Furthermore, we would like to reiterate that we’re still waiting for our internal teams to share elaborated steps on how to set up the Notifications endpoint using OAuth2. We appreciate your patience and understanding.
Hi, Thanks for the response. But if you see my above post from me. I have mentioned the scope we have authorized and below is that scope. it includes all the actions you have mentioned in the list Notifications | Coinbase Cloud
scope=wallet:accounts:read,wallet:addresses:read,wallet:buys:read,wallet:deposits:read,wallet:notifications:read,wallet:payment-methods:read,wallet:sells:read,wallet:transactions:read,wallet:user:read,wallet:withdrawals:read
But still, we are receiving only deposits event notification . when an withdrawal or buy or sale is created we aren’t notified.
Please advise, Thanks in advance.
Thanks,
Deepak Yagamurthy
Hi @nydeepak1 ! For your inquiry regarding the instance of not receiving a notification for withdrawals or orders placed, we will check this scenario with our internal teams to ensure that this is addressed accurately for you. We will get back to you once we have more information. We appreciate your utmost patience and understanding.
Hi @nydeepak1! We appreciate your patience as we check into this. As per confirmation with our internal teams, the probable reason as to why you’re not receiving a notification for withdrawals or orders placed is due to the notification being delayed. If notification delivery fails, it will be re-tried hourly for up to three days. If you ever need to access notifications afterwards, you can query them using notification API endpoints. You may read more details of the Notification Retry Schedule by going through this link.
Please feel free to let us know if you have any other questions.
Thank you for the response.
It’s been more than 24hrs, yet we don’t see any notifications for the withdrawals we have done. But deposit notifications are promptly notified within seconds.
Are we technically going in any wrong direction? We would like to know the detailed analysis of what is making the notifications pending for withdrawals, Buys & sells.
We tried calling the notification endpoints through OAuth2, unfortunately, we are getting the below response. We used the access token (Bearer) of an authorized user who has authorized our application.
{
“errors”: [
{
“id”: “invalid_authentication_method”,
“message”: “This endpoint is only available for API key authentication”
}
]
}
And also confirm whether to use client credentials or client access tokens or application users’ access tokens to access the notification URL. If it is a client access token, please advise how to get this.
Could you please us with this and wanted to check if there is any enterprise support like we could get On-call support from you.
Thank You! Looking forward to hearing from you.
Thanks,
Deepak Yagamurthy
Hello @nydeepak1! We appreciate your patience as we take a look into your concerns with our internal teams.
We would like to inform you that based on the information we have gathered, it seems that the notification you are utilizing was only setup for the API key hence, you are getting the error message “This endpoint is only available for API key authentication.” With this, we would like to suggest that if you are actually using the application via OAuth, you will need to setup the notification URL as well at the time you are creating a new OAuth application, or edit the properties of the OAuth2 application you are already utilizing.
You can do this by going into the Settings of your coinbase.com account and under the API tab, click on the + New OAuth2 Application button (if you’re creating a new OAuth2 app), or click on the Edit button beside the existing OAuth2 app (if you already had an OAuth2 app). Fill in the required details for the new OAuth2 application and in the “Notification URL Webhook for notifications” section, you have to input the URL where you will need to receive the webhook notifications.
Additionally, please note that unlike API keys, notifications for Coinbase Connect applications are initialized for application users who have an active access token. You could find more details about this in the documentation: Notifications | Coinbase Cloud
We hope this helps. Thank you and have a great day!
We have already configured OAuth2 as you mentioned in the previous response and we are receiving the notifications with the notification type “wallet:addresses:new-payment” promptly.
Unfortunately, we aren’t receiving any notifications of the below types
wallet:buys:created
wallet:buys:completed
wallet:buys:canceled
wallet:sells:created
wallet:sells:completed
wallet:sells:canceled
wallet:deposit:created
wallet:deposit:completed
wallet:deposit:canceled
wallet:withdrawal:created
wallet:withdrawal:completed
wallet:withdrawal:canceled
And the user has authorized the OAuth2 application with below scope.
wallet:accounts:read wallet:addresses:read wallet:buys:read wallet:deposits:read wallet:notifications:read wallet:payment-methods:read wallet:sells:read wallet:transactions:read wallet:user:read wallet:withdrawals:read
Please advise if we are missing anything. And also please help us with what needs to be done to receive notifications of all types.
Thank You! Looking forward to hearing from you
Thanks,
Deepak Yagamurthy
Hello @nydeepak1! We appreciate your patience. For OAuth2, permissions are set in the authorization URL. Some permissions like sending funds also require additional settings. Permissions are specified by including an additional scope parameter in OAuth2 request. Multiple permissions should be separated with a comma character in the URL. You can read more about them at Sign in with Coinbase permissions guide.
Moreover, can you please confirm if you have given the required scope parameter at the end of your request URL?
Example url : https://www.coinbase.com/oauth/authorize?response_type=code&client_id=YOUR_CLIENT_ID&redirect_uri=YOUR_CALLBACK_URL&scope=wallet:accounts:read,wallet:transactions:read
Additionally, please have a look on how to integrate Oauth2. Thank you!
Thank you for the response.
As you see in the above thread, We already mentioned all the steps we have performed and whatever you have given in the above response has already been followed as the documentation.
For reference, I have kept the link below that we are using for authorization. Please see below and advise if we are missing anything.
Please let us know if there is required any additional details.
Thanks,
Deepak Yagamurthy
Hi Team is there any update on the above request?