To pull data from the Binance API to Google Sheets easily and without writing any code, first install and open the Apipheny Google Sheets add-on.Apipheny is a no-code API integrator for Google Sheets that you can use to make unlimited API requests, connect to unlimited APIs (including the Binance API), save API requests, schedule API requests, and more. Click here if you want to learn more about Apipheny.
1.) Install Apipheny by clicking the Install button on this page.
2. After you’ve installed Apipheny, open a Google Sheet and then click on the Add-Ons option in the top menu. In the add-ons menu, you should see Apipheny.
Click Apipheny > Import API to open the Apipheny sidebar in your Google Sheets.
In order to access most Binance REST API endpoints, you will need an API key. To obtain an API key, follow the following instructions. If you already have your key you can skip this section.
1. After logging in to your Binance account, click API Management in the user center drop-down box:
2. If you did not install 2-factor authentication (2FA) when creating your Binance account, you will be asked to do add 2FA at this point:
In this example I chose SMS Authentication. Click the Send SMS button to receive a code on your mobile phone. After you have received the code, enter it in the SMS Verification Code section. You can also choose Google Authentication, which is more secure. After you add 2FA, this popup will disappear and you can continue obtaining your API key.
3. When the API management page finally opens, enter a name (label) for your private API key, and then click the Create button:
4. Next, fill in the Google Authentication Code or SMS Authentication Code again, to confirm the API Key creation for your account:
5. Once you have passed the 2FA Authentication, the system will send a confirmation email to the email address of your Binance account. You can go directly to your email or click the Go to email and verify button on the Binance page:
6. In the email, click the Confirm new API key button:
7. On the next page you will see your API key and Secret key. Remember to copy and paste your Secret Key somewhere safe, as it will not be shown again, due to security reasons. If you forget the Secret Key, you will need to delete the API key and then create a new one.
To explore endpoint URLs and query requirements, go the Binance API documentation page here: https://binance-docs.github.io/apidocs/spot/en/#general-info
All Binance endpoint URLs are created by appending an endpoint-specific path to the root URL:
For this example, we are using the API URL: https://api.binance.com/sapi/v1/margin/allPairs
If you want to use the same example URL as us, skip to the next section. If you want to create your own endpoint URL, keep reading.
For GET endpoints, parameters must be sent as a query string, while for POST, PUT, and DELETE endpoints, they may be sent either as a query string, or in the request body, with content type application/x-www-form-urlencoded.
No specific order is imposed on the parameters and both the query string and the request body approach can be used for the same query.
If your API endpoint needs to use an API key, then it must be sent through a dedicated X-MBX-APIKEY header:
“Signed” Binance API endpoints that require HMAC SHA256 will not currently work with our add-on, but endpoints that do not require HMAC SHA256 will work, such as the /allPairs endpoint we covered above. Some Binance API endpoints require HMAC SHA256 and others don’t. This tutorial goes through an example that doesn’t require HMAC SHA256.
The reason signed endpoints don’t currently work with our app is because they require an additional parameter called signature, a keyed HMAC SHA256 signature with your secretKey as the key and a concatenation of all the query’s parameters as the value passed to the HMAC operation.
Signed endpoints also require a timeStamp parameter, populated with the request’s millisecond timestamp:
An example of a signed endpoint is the Order API endpoint:
You can tell if an endpoint is signed or not because when you look at the documentation for that endpoint, it will say “(HMAC SHA256)” next to the URL.
Back in your Google Sheet, make sure the Apipheny add-on is open, on the “Import” tab.
After you’ve found the endpoint you need in Step 3, copy the complete URL into the API URL Path field in the Apipheny add-on, followed by any GET parameters required for your query (see screenshot below).
Here’s the example URL we used:
At the top of the add-on select the HTTP method (GET or POST) required by your API endpoint. For this example we are using GET.
Into the Headers section in Apipheny, you should add two rows with the following keys and values:
Key 1: Accept Value 1: application/json
your-API-key is the value you got in Step 2.
The Accept and X-MBX-APIKEY headers are required, so you should add them in the dedicated table, below the API URL Path (JSON / CSV) field:
It doesn’t matter what order you add the headers in.
Lastly, click the Run button at the bottom of the Apipheny add-on and then wait for the Binance API data to be imported into your Google Sheet.
After making a successful request to the Binance API, try querying a different endpoint, or try using one of the more advance features in the Apipheny add-on, such as: