Is there a way to track your staking positions? All the Savings positions seem to be easy to reference through the API but it doesn't appear that it supports any of the staking functionality (lists, positions, history, purchasing, etc).
I've poured through the Savings section of the API documentation but it doesn't seem to support staking, nor is it in the wallet endpoints.
You can get your current staking positions by doing a signed GET request to this endpoint
/sapi/v1/staking/position
And get your staking history through this endpoint
/sapi/v1/staking/stakingRecord
For more information about these endpoints and what parameters should be included in the requests, see the official Binance API documentation
Related
Kucoin provides an api for subaccount operations. For example: https://docs.kucoin.com/#get-account-balance-of-a-sub-account
Here, the request has the format: GET /api/v1/sub-accounts/{subUserId}
CCXT has no native support for sub-accounts by itself. However, it has support for exchange specific parameters (ie. fetch_balance(params={..}) - yet the documentation of these parameters is very poor.
Is there a way to fetch balance and create orders for kucoin subaccounts with CCXT?
I want to know some information using Opensea API that some NFT token is selling, but can't find info which api method can give so data. I tried to use events api method which displays all events info of token but can't find the difference between token which is selling and not. For example on the first picture token is selling, on the second one the token isn't
You can use opensea's api call retrieve assets. This will give you information about an asset and whether or not it is currently listed. As long as you have an api key, it will tell you if the asset is listed, and the details of that order. Hope it helps!
I use Coinbase API to generate Bitcoin addresses.
What are the limits of this API?
How many Bitcoin addresses can I generate?
The API says that:
The Coinbase API is rate limited to prevent abuse that would degrade our ability to maintain consistent API performance for all users. By default, each API key or app is rate limited at 10,000 requests per hour. If your requests are being rate limited, HTTP response code 429 will be returned with an rate_limit_exceeded error.
So I would reason to assume you can generate 10,000 BTC addresses per hour. Of course there might be somewhere else it has been mentioned.
API docs say it is unlimited for each account.
Address resource represents a bitcoin, bitcoin cash, litecoin or ethereum address for an account. Account can have unlimited amount of addresses and they should be used only once.
This text is taken from the official api docs (link down below) on date 04-02-2020
https://developers.coinbase.com/api/v2#addresses
I am developing a dashboard where all (direct) messages, tweets, etc directed at the user will be displayed in one dashboard. All the social media vendors have (OAuth) Rest APIs.
When developing a 3rd party program for an service like Twitter. Is it good practice to request data from the service's API every X milliseconds/seconds, or is there a better way?
It depends on which Twitter API you are interested in. Most of the REST API endpoints have published rate limits found here. If any of these suit your needs, then you would calculate the appropriate frequency of requests that would keep your from exceeding the rate limit.
Alternatively, if you are accessing Twitter's Streaming API, you would never close the connection.
Help me clarify terminology regarding the HTTP API.
Gateway URL and endpoints are the same thing, correct?
This is just the place to make a GET or POST call, correct?
Now for my question. It seams for each of the eBay API has its own gateway.
The Shopping API gate way is http://open.api.ebay.com/shopping?
I'm assuming the fallowing:
Finding: http://open.api.ebay.com/finding?
merchandising: http://open.api.ebay.com/merchandising?
... and so on.
Is this correct? or am I misunderstanding something.
Yes, the end point is the gateway. Each API has its own endpoint/gateway url. You would think that eBay would name their endpoints with the schema you provided, but they didn't. You will need to click on "Making a Call" after selecting the API you want the endpoint for in the documentation.
Example:
Here is the endpoint documentation for the Trading API, Shopping API, and Finding API.
Also you should know that not every endpoint is going to require the same info. For the trading API you are going to need a Token from the seller as well as your APP ID, whereas the shopping and trading API only needs the APP ID.