Security News
Input Validation Vulnerabilities Dominate MITRE's 2024 CWE Top 25 List
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
@beamnetwork/plaid
Advanced tools
A node.js client library for the Plaid API.
$ npm install plaid
You can specify the Plaid API version you wish to use when initializing plaid-node
. Releases prior to 2.6.x
do not support versioning.
const plaidClient = new plaid.Client({
clientID: process.env.PLAID_CLIENT_ID,
secret: process.env.PLAID_SECRET,
env: plaid.environments.sandbox,
options: {
version: '2019-05-29', // '2019-05-29' | '2018-05-22' | '2017-03-08'
},
});
For information about what has changed between versions and how to update your integration, head to the API upgrade guide.
The module supports all Plaid API endpoints. For complete information about the API, head to the docs.
All endpoints require a valid client_id
and secret
to
access and are accessible from a valid instance of a Plaid Client
:
const plaid = require('plaid');
const plaidClient = new plaid.Client({
clientID: client_id,
secret: secret,
env: plaid_env,
});
The plaid_env
parameter dictates which Plaid API environment you will access. Values are:
plaid.environments.production
- production use, creates Item
s on https://production.plaid.complaid.environments.development
- use for integration development and testing, creates Item
s on https://development.plaid.complaid.environments.sandbox
- quickly build out your integration with stateful test data, creates Item
s on https://sandbox.plaid.comThe options
field is optional and allows for clients to override the default options used to make requests. e.g.
const patientClient = new plaid.Client({
clientID: client_id,
secret: secret,
env: plaid_env,
options: {
timeout: 30 * 60 * 1000, // 30 minutes
version: '2019-05-29',
}
});
See here for a complete list of options. The default timeout for requests is 10 minutes.
Once an instance of the client has been created you use the following methods:
const plaid = require('plaid');
// Initialize client
const plaidClient = new plaid.Client({
clientID: client_id,
secret: secret,
env: plaid_env,
options: {
version: '2019-05-29',
},
});
// createPublicToken(String, Function)
plaidClient.createPublicToken(access_token, cb);
// exchangePublicToken(String, Function)
plaidClient.exchangePublicToken(public_token, cb);
// createProcessorToken(String, String, String, Function)
plaidClient.createProcessorToken(access_token, account_id, processor, cb);
// invalidateAccessToken(String, Function)
plaidClient.invalidateAccessToken(access_token, cb);
// removeItem(String, Function)
plaidClient.removeItem(access_token, cb);
// getItem(String, Function)
plaidClient.getItem(access_token, cb);
// importItem([String], Object, Object?, Function))
plaidClient.importItem(products, user_auth, options, cb)
// updateItemWebhook(String, String, Function)
plaidClient.updateItemWebhook(access_token, webhook, cb);
// getAccounts(String, Object?, Function)
plaidClient.getAccounts(access_token, options, cb);
// getBalance(String, Object?, Function)
plaidClient.getBalance(access_token, options, cb);
// getAuth(String, Object?, Function)
plaidClient.getAuth(access_token, options, cb);
// getIdentity(String, Function)
plaidClient.getIdentity(access_token, cb);
// getIncome(String, Function)
plaidClient.getIncome(access_token, cb);
// getCreditDetails(String, Function)
plaidClient.getCreditDetails(access_token, cb);
// getLiabilities(String, Function)
plaidClient.getLiabilities(access_token, cb);
// getDepositSwitch(String, Object?, Function)
plaidClient.getDepositSwitch(deposit_switch_id, options, cb)
// createDepositSwitch(String, String, Object?, Function)
plaidClient.createDepositSwitch(target_account_id, target_access_token, options, cb);
// createDepositSwitchToken(String, Function)
plaidClient.createDepositSwitchToken(deposit_switch_id, options, cb)
// getHoldings(String, Function)
plaidClient.getHoldings(access_token, cb);
// getInvestmentTransactions(String, Date(YYYY-MM-DD), Date(YYYY-MM-DD),
// Object?, Function)
plaidClient.getInvestmentTransactions(access_token, start_date, end_date, options, cb);
// getTransactions(String, Date(YYYY-MM-DD), Date(YYYY-MM-DD), Object?, Function)
plaidClient.getTransactions(access_token, start_date, end_date, options, cb);
// getAllTransactions(String, Date(YYYY-MM-DD), Date(YYYY-MM-DD), Object?, Function)
plaidClient.getAllTransactions(access_token, start_date, end_date, options, cb);
// refreshTransactions(String)
plaidClient.refreshTransactions(access_token);
// createStripeToken(String, String, Function)
plaidClient.createStripeToken(access_token, account_id, cb);
// getInstitutions(Number, Number, Object?, Function);
plaidClient.getInstitutions(count, offset, options, cb);
// getInstitutionsById(String, Object?, Function)
plaidClient.getInstitutionById(institution_id, options, cb);
// searchInstitutionsByName(String, [String], Object?, Function)
plaidClient.searchInstitutionsByName(query, products, options, cb);
// getCategories(Function)
plaidClient.getCategories(cb);
// getWebhookVerificationKey(String, Function)
plaidClient.getWebhookVerificationKey(key_id, cb);
// resetLogin(String, Function)
// Sandbox-only endpoint to trigger an `ITEM_LOGIN_REQUIRED` error
plaidClient.resetLogin(access_token, cb);
// Sandbox-only endpoint to trigger a webhook for an Item
plaidClient.sandboxItemFireWebhook(access_token, webhook_code, cb);
// Sandbox-only endpoint to set the verfication_status for an Item
plaidClient.sandboxItemSetVerificationStatus(access_token, account_id, verification_status, cb);
// Sandbox-only endpoint to create a `public_token`. Useful for writing integration tests without running Link.
plaidClient.sandboxPublicTokenCreate(institution_id, initial_products, options, cb);
All parameters except options
are required. If the options parameter is omitted, the last argument to the function
will be interpreted as the callback.
All requests have callbacks of the following form:
function callback(err, response) {
// err can be a network error or a Plaid API error (i.e. invalid credentials)
}
The err
argument passed to either callback style can either be an instance of Error
or a Plaid API error object. An Error
object
is only passed back in the case of a HTTP connection error. The following code distinguishes
between a Plaid error and a standard Error instance:
function callback(err, response) {
if (err != null) {
if (err instanceof plaid.PlaidError) {
// This is a Plaid error
console.log(err.error_code + ': ' + err.error_message);
} else {
// This is a connection error, an Error object
console.log(err.toString());
}
}
}
Exchange a public_token
from Plaid Link for a Plaid access_token
and then
retrieve account data:
plaidClient.exchangePublicToken(public_token, function(err, res) {
const access_token = res.access_token;
plaidClient.getAccounts(access_token, function(err, res) {
console.log(res.accounts);
});
});
Retrieve transactions for a transactions user for the last thirty days:
const now = moment();
const today = now.format('YYYY-MM-DD');
const thirtyDaysAgo = now.subtract(30, 'days').format('YYYY-MM-DD');
plaidClient.getTransactions(access_token, thirtyDaysAgo, today, (err, res) => {
console.log(`You have ${res.transactions.length} transactions from the last thirty days.`);
});
Get accounts for a particular Item
:
plaidClient.getAccounts(access_token, {
account_ids: ['123456790']
}, (err, res) => {
console.log(res.accounts);
});
// The library also juggles arguments, when options is omitted
plaidClient.getAccounts(access_token, (err, res) => {
console.log(res.accounts);
});
Every method returns a promise, so you don't have to use the callbacks.
API methods that return either a success or an error can be used with the
usual then/else
paradigm, e.g.
plaidPromise.then(successResponse => {
// ...
}).catch(err => {
// ...
});
For example:
'use strict';
const bodyParser = require('body-parser');
const express = require('express');
const plaid = require('plaid');
const plaidClient = new plaid.Client({
clientID: process.env.PLAID_CLIENT_ID,
secret: process.env.PLAID_SECRET,
env: plaid.environments.sandbox,
options: {
version: '2018-05-22',
},
});
const app = express();
const port = process.env.PORT || 3000;
app.use(bodyParser.urlencoded({
extended: true
}));
app.use(bodyParser.json());
app.post('/plaid_exchange', (req, res) => {
var public_token = req.body.public_token;
return plaidClient.exchangePublicToken(public_token)
.then(res => res.access_token)
.then(accessToken => plaidClient.getAccounts(accessToken))
.then(res => console.log(res.accounts))
.catch(err => {
// Indicates a network or runtime error.
if (!(err instanceof plaid.PlaidError)) {
res.sendStatus(500);
return;
}
// Indicates plaid API error
console.log('/exchange token returned an error', {
error_type: err.error_type,
error_code: res.statusCode,
error_message: err.error_message,
display_message: err.display_message,
request_id: err.request_id,
status_code: err.status_code,
});
// Inspect error_type to handle the error in your application
switch(err.error_type) {
case 'INVALID_REQUEST':
// ...
break;
case 'INVALID_INPUT':
// ...
break;
case 'RATE_LIMIT_EXCEEDED':
// ...
break;
case 'API_ERROR':
// ...
break;
case 'ITEM_ERROR':
// ...
break;
default:
// fallthrough
}
res.sendStatus(500);
});
});
app.listen(port, () => {
console.log(`Listening on port ${ port }`);
});
Open an issue!
Click here!
FAQs
A node.js client for the Plaid API
The npm package @beamnetwork/plaid receives a total of 0 weekly downloads. As such, @beamnetwork/plaid popularity was classified as not popular.
We found that @beamnetwork/plaid demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 8 open source maintainers 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
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.