Recently (perhaps since a week) I am receiving a 404 from /api/v3/brokerage/orders/edit/ as per Coinbase Cloud.
Interestingly if I send a dud payload, I get the below:
‘{“error”:“unknown”,“error_details”:“proto:\xa0(line 1:2): unknown field \“huzzah\””,“message”:“proto:\xa0(line 1:2): unknown field \“huzzah\””}’
If, however I send a seemingly valid payload, I get the 404:
Is this some sort of joke? You knock out a core endpoint for ORDER MANAGEMENT and it takes you a week to respond on the forum and 11 days we still cannot edit orders effectively? Are you actively trying to drop users?
Added Edit Order which allows users to edit orders. Only limit order types, with time in force type of good-till-cancelled can be edited.
Added Edit Order Preview which allows users to preview an edit request’s results. Only limit order types, with time in force type of good-till-cancelled can be previewed for an edit.
What do you think think people are using the API for, dog grooming? I’m glad you have an opinion; the rest of us that are running live systems with order optimization/management strongly “disagree”.
@RobV May I ask? Did you have access to that API before it was made public for everyone? Otherwise you surly can manage orders the way you did before this API endpoint was added, no?
Don’t get me wrong - it is disaster. API was available less then month and it is already broken… Their status page shows that this is problem since 1st December. That is not acceptable!
This raises question - can you trust this API at all… They are pushing changes/updates/fixes without any notice.
Anyway good luck running live systems with this API.
I am also receiving similar errors related to the v2/accounts endpoint and v2/brokerage/accounts endpoint. This is a massive issue, as you need the account_id these endpoints return in order to make subsequent calls.
Apologies for the delay. The issues we were fixing were related to a race condition at high scale, causing some odd behavior that was difficult to replicate. In the interest of accuracy and trust, we took extra time to develop a comprehensive testing framework before launching our fix, and we’re keeping a close eye on this.
The edit endpoint is operational. We have pinged someone to resolve the status page incident since I unfortunately don’t have access to edit the message.