This Berbix Node library provides simple interfaces to interact with the Berbix API.
If you are using NPM for package management
npm install berbix
If you are using Yarn for package management
yarn add berbix
// Import the Berbix Node library
var berbix = require('berbix');
// Construct the client, providing your API secret
var client = new berbix.Client({
apiSecret: 'your_api_secret_here',
})
var transactionTokens = await client.createTransaction({
customerUid: "internal_customer_uid", // ID for the user in internal database
templateKey: "your_template_key", // Template key for this transaction
})
// Load refresh token from database
var transactionTokens = berbix.Tokens.fromRefresh(refreshToken)
var transactionData = await client.fetchTransaction(transactionTokens)
Supported options:
apiSecret(required) - The API secret that can be found in your Berbix Dashboard.httpClient- An optional override for the default Node HTTP client.
Creates a transaction within Berbix to initialize the client SDK. Typically after creating a transaction, you will want to store the refresh token in your database associated with the currently active user session.
Supported options:
email- Previously verified email address for a user.phone- Previously verified phone number for a user.customerUid- An ID or identifier for the user in your system.templateKey- The template key for this transaction.hostedOptions- Optional configuration object for creating hosted transactions. ThehostedOptionsobject can optionally include the following fields:completionEmail- Email address to which completion alerts will be sent for this transaction.redirectUrl- URL to redirect the user to after they complete the transaction. If not specified, the URL specified in the Berbix dashboard will be used instead.
Fetches all of the information associated with the transaction. If the user has already completed the steps of the transaction, then this will include all of the elements of the transaction payload as described on the Berbix developer docs.
This is typically not needed to be called explicitly as it will be called by the higher-level SDK methods, but can be used to get fresh client or access tokens.
This method validates that the content of the webhook has not been forged. This should be called for every endpoint that is configured to receive a webhook from Berbix.
Parameters:
secret- This is the secret associated with that webhook. NOTE: This is distinct from the API secret and can be found on the webhook configuration page of the dashboard.body- The full request body from the webhook. This should take the raw request body prior to parsing.header- The value in the 'X-Berbix-Signature' header.
Permanently deletes all submitted data associated with the transaction corresponding to the tokens provided.
Changes a transaction's "action", for example upon review in your systems. Returns the updated transaction upon success.
Parameters:
action: string- A string describing the action taken on the transaction. Typically this will either be "accept" or "reject".note: string- A string containing an optional note explaining the action taken.
Completes a previously created transaction, and overrides its return payload and flags to match the provided parameters.
Parameters:
responsePayload: string- A string describing the payload type to return when fetching transaction metadata, e.g. "us-dl". See our testing guide for possible options.flags: string[]- An optional list of flags to associate with the transaction (independent of the payload's contents), e.g. ["id_under_18", "id_under_21"]. See our flags documentation for a list of flags.overrideFields: { string: string }- An optional mapping from a transaction field to the desired override value, e.g.params.overrideFields = { "date_of_birth": "2000-12-09" }
This is the short-lived bearer token that the backend SDK uses to identify requests associated with a given transaction. This is not typically needed when using the higher-level SDK methods.
This is the short-lived token that the frontend SDK uses to identify requests associated with a given transaction. After transaction creation, this will typically be sent to a frontend SDK.
This is the long-lived token that allows you to create new tokens after the short-lived tokens have expired. This is typically stored in the database associated with the given user session.
The internal Berbix ID number associated with the transaction.
The time at which the access and client tokens will expire.
Creates a tokens object from a refresh token, which can be passed to higher-level SDK methods. The SDK will handle refreshing the tokens for accessing relevant data.
npm publish