subscribe: 0 in api call to be deprecated soon (v3)

edited October 28 in General

Please note this has been released and subscribe call is deprecated

Please note that we will soon deprecate subscribe: 0 calls from all of our streaming calls as they lead to lots of confusion.

As of now subscribe: 1 subscribes you to call and developers expects subscribe: 0 to unsubscribe from previous call, but that's not the case as subscribe: 0 just mean that don't subscribe to this call.

So to make it more consistent and less confusing for developers we are going to remove subscribe: 0 feature.

If you want to subscribe to call send subscribe: 1 and if you don't want to subscribe don't send subscribe in that call.

So in future call like this

{
  "ticks_history": "AS51",
  "granularity": 900,
  "subscribe": 0,
  "count": 1000,
  "end": "latest",
  "style": "candles",
  "start": 1451581739,
  "adjust_start_time": 1,
  "req_id": 14
}

will result in error like this

{
  "echo_req": {
    "count": 1000,
    "granularity": 900,
    "req_id": 14,
    "ticks_history": "AS51",
    "subscribe": 0,
    "style": "candles",
    "end": "latest",
    "adjust_start_time": 1,
    "start": 1451581739
  },
  "req_id": 14,
  "error": {
    "details": {
      "subscribe": "does not match the regex pattern ^1$"
    },
    "message": "Input validation failed: subscribe",
    "code": "InputValidationFailed"
  },
  "msg_type": "error"
}

Please use forget and forget_all calls for unsubscribing from call

This discussion has been closed.