
Security News
Crates.io Users Targeted by Phishing Emails
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
kraken-cryptoexchange-api
Advanced tools
This package provides a modern javascript solution for interfacing with the Kraken cryptoexchange API. Currently, only the REST API has been implemented. Support for for the Push API is in the works.
This library is intended to be used with ES6, TypeScript, etc. In the interest of moving towards the more-readable
async/await
pattern, callbacks are not supported. Only native Promise-based interaction is supported.
This library does not track your request rate. Kraken throttles/disables api access if the request rate exceeds certain limits. It is the responsibility of the user to track rate limits.
npm i kraken-cryptoexchange-api
yarn add kraken-cryptoexchange-api
import { getClient, IKrakenClient } from 'kraken-cryptoexchange-api';
const main = async (): Promise<{}> => {
try {
const client: IKrakenClient = getClient({
publicKey : '', // Your public key
privateKey: '', // Your private key
});
const { status, data } = await client.getAccountBalance();
return Promise.resolve(data);
} catch (err) {
return Promise.reject(err);
}
};
main().then(data => console.log(data))
.catch(err => console.error(err));
This example shows usage without async/await
.
const kraken = require('kraken-cryptoexchange-api');
const client = kraken.getClient({
publicKey : '', // Your public key
privateKey: '', // Your private key
});
client.getAccountBalance()
.then(response => {
const { status, data } = response;
console.log(data);
})
.catch(err => console.error(err));
Note: the remainder of this README.md will use TypeScript examples.
This project leverages the axios package under the hood. All request configuration is forwarded to the underlying request architecture. See the documentation for more information.
All endpoints are available via the client. If authentication keys are provided during client construction, public and private endpoints will succeed. If no keys are given, only public endpoints will succeed. Private endpoints will return a promise rejection when not authenticated, so be sure to properly trap your errors.
No attempt is made to mitigate private calls when not authenticated. It is the responsibility of the user to trap any errors resulting from incorrect/invalid authentication
A few convenience properties and methods are provided:
This gives the user access to the underlying request forwarder. While not very useful to a user, it does expose the
request signing algorithm via rawAgent#signMessage
.
This method returns a boolean corresponding to whether or not the user has provided API keys to the client.
This method allows a user to upgrade a public client with credentials. If the client already has credentials, this method will replace the existing keys.
In order to place requests with public endpoints, simply instantiate the client with no parameters:
const client: IKrakenClient = getClient();
In order to authenticate a client with the Kraken API, a private request must provide a public key and a correctly signed request. This library handles request signatures - the user simply provides a public/private key pair. You can generate your own API keys through the Kraken interface.
FAQs
Simple typescript interface to the Kraken cryptoexchange.
The npm package kraken-cryptoexchange-api receives a total of 3 weekly downloads. As such, kraken-cryptoexchange-api popularity was classified as not popular.
We found that kraken-cryptoexchange-api demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
Product
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
Product
Socket's Rust support is moving to Beta: all users can scan Cargo projects and generate SBOMs, including Cargo.toml-only crates, with Rust-aware supply chain checks.