
Security News
The Next Open Source Security Race: Triage at Machine Speed
Claude Opus 4.6 has uncovered more than 500 open source vulnerabilities, raising new considerations for disclosure, triage, and patching at scale.
@onfido/api
Advanced tools
The official Node.js library for integrating with the Onfido API.
Documentation is available at https://documentation.onfido.com.
This library is for backend use only, as it requires secret Onfido API tokens and should not be used in the frontend due to security reasons.
If you need to collect applicant data in the frontend of your application, we recommend that you use the Onfido SDKs:
This version uses Onfido API v3.6. Refer to our API versioning guide for details of which client library versions use which versions of the API.
npm install @onfido/api
yarn add @onfido/api
Require the package:
const {
DefaultApi,
Configuration,
WebhookEventVerifier,
} = require("@onfido/api");
const { isAxiosError } = require("axios");
For TypeScript users, types are available as well:
import {
DefaultApi,
Configuration,
Region,
WebhookEventVerifier,
} from "@onfido/api";
import { isAxiosError } from "axios";
Configure with your API token and region:
const onfido = new DefaultApi(
new Configuration({
apiToken: process.env.ONFIDO_API_TOKEN,
region: Region.EU, // Supports Region.EU (Europe), Region.US (United States), and Region.CA (Canada)
baseOptions: { timeout: 60_000 }, // Additional Axios options (timeout, etc.)
}),
);
NB: by default, timeout is set to 30 seconds.
Using async/await (in an async function):
(async () => {
try {
const applicant = await onfido.createApplicant({
first_name: "Jane",
last_name: "Doe",
location: {
ip_address: "127.0.0.1",
country_of_residence: "GBR",
},
});
// ...
} catch (error) {
if (isAxiosError(error)) {
console.log(`status code: ${error.response?.status}`);
const error_details = error.response?.data.error;
// An error response was received from the Onfido API, extra info is available.
if (error_details) {
console.log(error_details.message);
console.log(error_details.type);
} else {
// No response was received for some reason e.g. a network error.
console.log(error.message);
}
} else {
console.log(error.message);
}
}
})();
Please find more information regarding Axios errors in library documentation.
Using promises:
onfido
.createApplicant({
first_name: "Jane",
last_name: "Doe",
location: {
ip_address: "127.0.0.1",
country_of_residence: "GBR"
}
})
.then(applicant =>
onfido.createCheck({
applicant_id: applicant.data.id,
report_names: ["identity_enhanced"]
})
)
.then(check =>
// Handle successfully created check.
)
.catch(error => {
// Handle error.
});
File downloads, for example onfido.downloadDocument(documentId), will return an instance of a FileTransfer object.
This object will have a content type, e.g. image/png.
download.headers["content-type"];
Call slice() to get a Buffer of the download:
const blob = download.data.slice();
File upload should make use of the provided FileTransfer class, e.g.:
onfido.uploadDocument(
"passport",
"<APPLICANT_ID>",
new FileTransfer(Buffer.from(document.buffer), document.filename),
);
FileTransfer object can also be created from an existing file, e.g. new FileTransfer("path/to/passport.png").
Webhook events payload needs to be verified before it can be accessed. Verifying webhook payloads is crucial for security reasons, as it ensures that the payloads are indeed from Onfido and have not been tampered with. The library allows you to easily decode the payload and verify its signature before returning it as an object for user convenience:
(async () => {
try {
const token = process.env.ONFIDO_WEBHOOK_SECRET_TOKEN;
const verifier = new WebhookEventVerifier(token);
const signature = "a0...760e";
const event = verifier.readPayload(`{"payload":{"r...3"}}`, signature);
} catch (e) {
if (e instanceof OnfidoInvalidSignatureError) {
// Invalid webhook signature
}
}
})();
Except for accessing Task object's outputs, avoid using the square bracket syntax (i.e. []) to access undefined properties to prevent breaking changes when these fields appear.
This library is automatically generated using OpenAPI Generator (version: 7.11.0); therefore, all contributions (except test files) should target the Onfido OpenAPI specification repository instead of this repository. Please follow the contribution guidelines provided in the OpenAPI specification repository.
For contributions to the tests instead, please follow the steps below:
git checkout -b my-new-feature)git commit -am 'Add detailed description of the feature')git push origin my-new-feature)Versioning helps manage changes and ensures compatibility across different versions of the library.
Semantic Versioning policy is used for library versioning, following the guidelines and limitations outlined below:
Additional documentation and code examples can be found at https://documentation.onfido.com.
Should you encounter any technical issues during integration, please contact Onfido's Customer Support team via the Customer Experience Portal which also includes support documentation.
FAQs
Node.js library for the Onfido API
The npm package @onfido/api receives a total of 71,139 weekly downloads. As such, @onfido/api popularity was classified as popular.
We found that @onfido/api demonstrated a healthy version release cadence and project activity because the last version was released less than 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
Claude Opus 4.6 has uncovered more than 500 open source vulnerabilities, raising new considerations for disclosure, triage, and patching at scale.

Research
/Security News
Malicious dYdX client packages were published to npm and PyPI after a maintainer compromise, enabling wallet credential theft and remote code execution.

Security News
gem.coop is testing registry-level dependency cooldowns to limit exposure during the brief window when malicious gems are most likely to spread.