Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some v1 endpoints get deprecated "By end of Q1 2020" #556

Closed
normoes opened this issue Jul 21, 2020 · 0 comments · Fixed by #557
Closed

Some v1 endpoints get deprecated "By end of Q1 2020" #556

normoes opened this issue Jul 21, 2020 · 0 comments · Fixed by #557

Comments

@normoes
Copy link
Contributor

normoes commented Jul 21, 2020

In the Binance changelog for 2019-11-13 it is said:

Deprecation of v1 endpoints:
By end of Q1 2020, the following endpoints will be removed from the API. The documentation has been updated to use the v3 versions of these endpoints.

  • GET api/v1/depth
  • GET api/v1/historicalTrades
  • GET api/v1/aggTrades
  • GET api/v1/klines
  • GET api/v1/ticker/24hr
  • GET api/v1/ticker/price
  • GET api/v1/exchangeInfo
  • POST api/v1/userDataStream
  • PUT api/v1/userDataStream
  • GET api/v1/ping
  • GET api/v1/time
  • GET api/v1/ticker/bookTicker

These endpoints however, will NOT be migrated to v3. Please use the following endpoints instead moving forward.

Old V1 Endpoints New V3 Endpoints
GET api/v1/ticker/allPrices GET api/v3/ticker/price
GET api/v1/ticker/allBookTickers GET api/v3/ticker/bookTicker

Is ithis something that needs consideration?

In the source code, I can see something like:

return self._get('depth', data=params)

with

 def _get(self, path, signed=False, version=PUBLIC_API_VERSION, **kwargs):

and

PUBLIC_API_VERSION = 'v1'

Best regards.
Norman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant