I am new to using APIs and was trying to build a trading bot in python using WazirX exchange's REST API. I am unable to understand how to make API calls using their documentation (Also, is this an example of a good API documentation or of a bad one?). Can anyone point to any python wrapper libraries through which I can execute trades using an API key and secret? I tried searching a lot but couldn't find any Github repository using their API to execute trades (I have seen some using the public endpoints only).
Any help would be appreciated.
Wazirx itself has provided Ruby and Python connectors
There are also 3rd party libraries available which can be used.
https://docs.wazirx.com/#api-third-party-integrations
Related
I'm currently trying to develop an application to use ms-graph API using python.
I'm trying to use SSO authentication but I cant find any resources or documentation related.
I found this documentation https://learn.microsoft.com/en-us/office/dev/add-ins/develop/sso-in-office-add-ins
but it is only for javascript.
I wrote a script using Flask and another script using O365 python package.
It doesnt seem like its a Single sign on application that I try to achieve...
I'm looking for any documentation that could help.
You are referring to the Office web add-ins where you could also use SSO. But it seems you are developing a standalone application where Graph API is used. In that case you may find the Configure SAML-based single sign-on for your application using the Microsoft Graph API tutorial helpful.
I am looking for examples or actual documentation for Train level Openstack Octavia (Load Balancer component) python API. Everything in the OS project doc site seems to be focused on the CLI. I would like an example and possible API specification (what to pass in, what to expect out of the functions defined for the OctaviaAPI class in the component. I have been looking for a few hours with little success.
Try https://docs.openstack.org/openstacksdk/latest/user/proxies/load_balancer_v2.html. In general, projects' documentation sites don't cover Python bindings, as they are not part of the projects. OpenstackSDK is its own project.
Yeah, the client based python binds are being phased out in favor of the openstacksdk. Octavia went straight to using openstacksdk for the python bindings.
I am looking at using google cloud python SDKs to manage my resources. I am not able to find compute module in the python SDK.
Python Doc here: https://googlecloudplatform.github.io/google-cloud-python/latest/
However compute module is available in Node.js SDK.
Node.js Doc here: https://googlecloudplatform.github.io/google-cloud-node/#/docs/google-cloud/0.56.0/compute
Can I get information if this module(compute) is available in python?
If not is this being planned and when can I expect it.
The google-cloud-python project you link to is hand-crafted pythonic libraries for GCP APIs. There is not yet one for Compute.
Instead you will have to use the auto-generated Python client library. See https://cloud.google.com/compute/docs/tutorials/python-guide for an example.
How to connect to and handle Wit.ai actions and intents from local machine?
i.e sending query to wit.ai using python api's and performing actions on local machine depend on json response.
I cannot find any proper documentation regarding this.
Almost all the tutorials are using node.js
Thanks in advance.
In fact, there is a Python SDK on the Wit.ai site.
There are also few examples that should help you get up to speed.
You may first want to check the quickstart.py example, that corresponds to the Build your first app tutorial on the Wit.ai site.
The documentation of the wit.ai contains the Github repository for python Library pywit.
You can check those examples for better understanding of the python code needed to develop chatbot.
Since you asked for documentations and other useful materials, you can check these blogs and github repos
How to make a basic ChatBot (Wit.ai) Part-1
Fb Bot tutorial along with integration
Wit.ai API provides many kind of NLP services including Speech Recognition. Follow this link for more information.
I searched for Python API to interact with google bigquery. And I found two packages provides similar APIs: Google BigQuery Client(Part of Google API Client Package googleapiclient) and Gcloud package gcloud.
Here are the documentation about using these two APIs for Bigquery:
Google API Client:googleapiclient
https://developers.google.com/resources/api-libraries/documentation/bigquery/v2/python/latest/index.html
https://cloud.google.com/bigquery/docs/reference/v2/
Google Cloud package: gcloud
http://googlecloudplatform.github.io/gcloud-python/stable/bigquery-usage.html
Both packages are from google, and provides similar functionalities interacting with bigquery. I have the following confusions:
It seems both package includes a wide range of functionalities of Google Cloud Platform. In my view, gcloud provides commandline tool and local environment setup. Generally, what are the differences of these two packages?
In terms of python module, what are the differences of their usage?
Is there any relation between these two packages?
Which is more suitable for accessing Bigquery?
What kind of job are they suitable for?
The googleapiclient client is generated directly from the raw API definition (the definition is a json file, hosted here.)
Because it is automatically generated, it is not what any sane python programmer would do if they were trying to write a python client for BigQuery. That said, it is the lowest-level representation of the API.
The gcloud client, on the other hand, was what a group of more-or-less sane folks at Google came up with when they tried to figure out what a client should look like for BigQuery. It is really quite nice, and lets you focus on what's important rather than converting results from the strange f/v format used in the BigQuery API into something useful.
Additionally, the documentation for the gcloud API was written by a doc writer. The documentation for the googleapiclient was, like the code, automatically generated from a definition of the API.
My advice, having used both (and having, mostly unsuccessfully, helped design the BigQuery API to try to make the generated client behave reasonably), is to use the gcloud client. It will handle a bunch of low-level details for you and generally make your life easier.