I can introduce you a stretch on the basis of information imposed on you.
Ethereum API -The -PROSAGE: A hand -running by shooting NEAR
As a delay, you, rightly, looked at the situation when your invited Ethereum API does not pass, it is not clear to the fact that the hand -running documentation. In this state, we dissatisfied with some other questioning and the implementation to help them grind them.
What has fallen wrong?
Before you subtress the shooting of the neo -paddock, let’s mind that it is not so in your case:
- You have said “Apisecret” as a part, but you did not submit its values to the code.
- In the documentation, API recommends that you need to use the “sign” method with the “crypto” of the “Axios” for subscribing transaction ethereum.
###
1. Specify Apisecret
To solve this problem, obligatory indicate the value of the expiry apisecret
in your code:
`Javascript
const apisecret = 'Your_api_secret_key_here';
Change your_api_secret_key_hee '' 'on the factual" apisecret "value submitted by binance.
2. UsingCrypto.sign ()Method
To sign the transaction of Ethereum, you should use the methodCrypto ‘ObjectSint ()
Axios. Here's a conjugated code fragment:
Javascript
Const Axios = require ('Axios');
Const Crypto = Require ('Crypto');
const apisecret = 'Your_api_secret_key_here';
Axios.post ('/API/V1/Sign', {
Signature: Aviser,
Data: {
// Your data on transaction ethereum goes here
}
})
.then ((Answer) => {
Console.log (Response.data);
})
.catch ((liner) => {
Console.error (Oshbak);
});
Obligatory change '/API/v1/sign' the factual URL of the score, the binance.
LOCAL COOLS
For the further shooting shooting your sight API disseminate the following:
- Tie Documentation Binance API on the subject of any concrete treats or ogricing.
- Revenge that you have unwavering decrees and ucerels to access to API.
- If you use the library, such asAxios`, beate that she is a consignment with API Binance.
Record these issues, you will be able to grind the nonsense of the Ethereum API and firmly sign your transaction.