Remove a rate alert
Stop watching a threshold. Deleting rather than deactivating: an alert is a small, cheap thing to set again, and a list cluttered with switched-off rows is one nobody reads. The notifications it already sent are unaffected — they are a record of what the rate did, not of what is being watched now.
Stop watching a threshold.
Deleting rather than deactivating: an alert is a small, cheap thing to set again, and a list cluttered with switched-off rows is one nobody reads. The notifications it already sent are unaffected — they are a record of what the rate did, not of what is being watched now.
Authorization
OAuth2PasswordBearer In: header
Path Parameters
uuidCookie Parameters
Response Body
application/json
curl -X DELETE "https://example.com/api/b/v1/fx/alerts/497f6eca-6276-4993-bfeb-53cbbbba6f08"Set a rate alert POST
Watch a pair and notify when it crosses `rate`. 409 when the condition already holds. An alert fires on the rate *crossing* the threshold rather than on it being past it, so one set above a rate that is already higher could not fire until the rate first fell back — storing it would hand somebody a control that looks armed and is not. The error says what the rate is now, which is the thing they were asking about. 409 too when the same threshold is already set on the same pair: that is a double-click rather than a second intention.
Display currency GET
Next Page