Developer-friendly & type-safe TypeScript SDK for the Kombo Unified API.
Warning
The Kombo TypeScript SDK is still in beta and is subject to breaking changes.
The SDK can be installed with either npm, pnpm, bun or yarn package managers.
npm add @kombo-api/sdkpnpm add @kombo-api/sdkbun add @kombo-api/sdkyarn add @kombo-api/sdkNote
This package is published as an ES Module (ESM) only. For applications using
CommonJS, use await import("@kombo-api/sdk") to import and use this package.
import { Kombo } from "@kombo-api/sdk";
const kombo = new Kombo({
api_key: "<YOUR_BEARER_TOKEN_HERE>",
});
async function run() {
const result = await kombo.general.checkApiKey();
console.log(result);
}
run();The majority of Kombo API endpoints are for interacting with a single "integration" (i.e., a single connection to one your customers' systems). For using these, make sure to specify the integration_id parameter when initializing the SDK:
import { Kombo } from "@kombo-api/sdk";
const kombo = new Kombo({
api_key: "<YOUR_BEARER_TOKEN_HERE>",
integration_id: "workday:HWUTwvyx2wLoSUHphiWVrp28",
});
async function run() {
const result = await kombo.hris.getEmployees();
console.log(result);
}
run();The Kombo platform is available in two regions: Europe and United States.
By default, the SDK will use the EU region. If you're using the US region (hosted under api.us.kombo.dev), make sure to specify the server parameter when initializing the SDK.
import { Kombo } from "@kombo-api/sdk";
const kombo = new Kombo({
server: "us",
api_key: "<YOUR_BEARER_TOKEN_HERE>",
});Available methods
- getPackages - Get packages
- setPackages - Set packages
- getOpenOrders - Get open orders
- updateOrderResult - Update order result
- getApplications - Get applications
- moveApplicationToStage - Move application to stage
- addApplicationResultLink - Add result link to application
- addApplicationNote - Add note to application
- getApplicationAttachments - Get application attachments
- addApplicationAttachment - Add attachment to application
- rejectApplication - Reject application
- getCandidates - Get candidates
- createCandidate - Create candidate
- getCandidateAttachments - Get candidate attachments
- addCandidateAttachment - Add attachment to candidate
- addCandidateResultLink - Add result link to candidate
- addCandidateTag - Add tag to candidate
- removeCandidateTag - Remove tag from candidate
- getTags - Get tags
- getApplicationStages - Get application stages
- getJobs - Get jobs
- createApplication - Create application
- getUsers - Get users
- getOffers - Get offers
- getRejectionReasons - Get rejection reasons
- getInterviews - Get interviews
- importTrackedApplication - Import tracked application
- createConnectionLink - Create connection link
- getIntegrationByToken - Get integration by token
- checkApiKey - Check API key
- triggerSync - Trigger sync
- sendPassthroughRequest - Send passthrough request
- deleteIntegration - Delete integration
- getIntegrationDetails - Get integration details
- createReconnectionLink - Create reconnection link
- getIntegrationFields - Get integration fields
- updateIntegrationField - Updates an integration fields passthrough setting
- getCustomFields - Get custom fields with current mappings
- updateCustomFieldMapping - Put custom field mappings
- getTools - Get tools
- getEmployees - Get employees
- getEmployeeForm - Get employee form
- createEmployeeWithForm - Create employee with form
- addEmployeeDocument - Add document to employee
- getEmployeeDocumentCategories - Get employee document categories
- getGroups - Get groups
- getEmployments - Get employments
- getLocations - Get work locations
- getAbsenceTypes - Get absence types
- getTimeOffBalances - Get time off balances
- getAbsences - Get absences
- createAbsence - Create absence
- deleteAbsence - Delete absence
- getLegalEntities - Get legal entities
- getTimesheets - Get timesheets
- getPerformanceReviewCycles - Get performance review cycles
- getPerformanceReviews - Get performance reviews
Some of the endpoints in this SDK support pagination. To use pagination, you
make your SDK calls as usual, but the returned response object will also be an
async iterable that can be consumed using the for await...of
syntax.
Here's an example of one such pagination call:
import { Kombo } from "@kombo-api/sdk";
const kombo = new Kombo({
api_key: "<YOUR_BEARER_TOKEN_HERE>",
});
async function run() {
const result = await kombo.general.getIntegrationFields({
integration_id: "<id>",
});
for await (const page of result) {
console.log(page);
}
}
run();KomboError is the base class for all HTTP error responses. It has the following properties:
| Property | Type | Description |
|---|---|---|
error.message |
string |
Error message |
error.statusCode |
number |
HTTP response status code eg 404 |
error.headers |
Headers |
HTTP response headers |
error.body |
string |
HTTP body. Can be empty string if no body is returned. |
error.rawResponse |
Response |
Raw HTTP response |
error.data$ |
Optional. Some errors may contain structured data. See Error Classes. |
import { Kombo } from "@kombo-api/sdk";
import * as errors from "@kombo-api/sdk/models/errors";
const kombo = new Kombo({
api_key: "<YOUR_BEARER_TOKEN_HERE>",
});
async function run() {
try {
const result = await kombo.general.checkApiKey();
console.log(result);
} catch (error) {
// The base class for HTTP error responses
if (error instanceof errors.KomboError) {
console.log(error.message);
console.log(error.statusCode);
console.log(error.body);
console.log(error.headers);
// Depending on the method different errors may be thrown
if (error instanceof errors.KomboGeneralError) {
console.log(error.data$.status); // models.KomboGeneralErrorStatus
console.log(error.data$.error); // models.KomboGeneralErrorError
}
}
}
}
run();Primary error:
KomboError: The base class for HTTP error responses.
Less common errors (9)
Network errors:
ConnectionError: HTTP client was unable to make a request to a server.RequestTimeoutError: HTTP request timed out due to an AbortSignal signal.RequestAbortedError: HTTP request was aborted by the client.InvalidRequestError: Any input used to create a request is invalid.UnexpectedClientError: Unrecognised or unexpected error.
Inherit from KomboError:
KomboAtsError: The standard error response with the error codes for the ATS use case. Applicable to 27 of 57 methods.*KomboHrisError: The standard error response with the error codes for the HRIS use case. Applicable to 17 of 57 methods.*KomboGeneralError: The standard error response with just the platform error codes. Applicable to 13 of 57 methods.*ResponseValidationError: Type mismatch between the data returned from the server and the structure expected by the SDK. Seeerror.rawValuefor the raw value anderror.pretty()for a nicely formatted multi-line string.
* Check the method documentation to see if the error is applicable.
Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.
To change the default retry strategy for a single API call, simply provide a retryConfig object to the call:
import { Kombo } from "@kombo-api/sdk";
const kombo = new Kombo({
api_key: "<YOUR_BEARER_TOKEN_HERE>",
});
async function run() {
const result = await kombo.general.checkApiKey({
retries: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
});
console.log(result);
}
run();If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:
import { Kombo } from "@kombo-api/sdk";
const kombo = new Kombo({
retry_config: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
api_key: "<YOUR_BEARER_TOKEN_HERE>",
});
async function run() {
const result = await kombo.general.checkApiKey();
console.log(result);
}
run();All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.
To read more about standalone functions, check FUNCTIONS.md.
Available standalone functions
assessmentGetOpenOrders- Get open ordersassessmentGetPackages- Get packagesassessmentSetPackages- Set packagesassessmentUpdateOrderResult- Update order resultatsAddApplicationAttachment- Add attachment to applicationatsAddApplicationNote- Add note to applicationatsAddApplicationResultLink- Add result link to applicationatsAddCandidateAttachment- Add attachment to candidateatsAddCandidateResultLink- Add result link to candidateatsAddCandidateTag- Add tag to candidateatsCreateApplication- Create applicationatsCreateCandidate- Create candidateatsGetApplicationAttachments- Get application attachmentsatsGetApplications- Get applicationsatsGetApplicationStages- Get application stagesatsGetCandidateAttachments- Get candidate attachmentsatsGetCandidates- Get candidatesatsGetInterviews- Get interviewsatsGetJobs- Get jobsatsGetOffers- Get offersatsGetRejectionReasons- Get rejection reasonsatsGetTags- Get tagsatsGetUsers- Get usersatsImportTrackedApplication- Import tracked applicationatsMoveApplicationToStage- Move application to stageatsRejectApplication- Reject applicationatsRemoveCandidateTag- Remove tag from candidateconnectCreateConnectionLink- Create connection linkconnectGetIntegrationByToken- Get integration by tokengeneralCheckApiKey- Check API keygeneralCreateReconnectionLink- Create reconnection linkgeneralDeleteIntegration- Delete integrationgeneralGetCustomFields- Get custom fields with current mappingsgeneralGetIntegrationDetails- Get integration detailsgeneralGetIntegrationFields- Get integration fieldsgeneralGetTools- Get toolsgeneralSendPassthroughRequest- Send passthrough requestgeneralTriggerSync- Trigger syncgeneralUpdateCustomFieldMapping- Put custom field mappingsgeneralUpdateIntegrationField- Updates an integration fields passthrough settinghrisAddEmployeeDocument- Add document to employeehrisCreateAbsence- Create absencehrisCreateEmployeeWithForm- Create employee with formhrisDeleteAbsence- Delete absencehrisGetAbsences- Get absenceshrisGetAbsenceTypes- Get absence typeshrisGetEmployeeDocumentCategories- Get employee document categorieshrisGetEmployeeForm- Get employee formhrisGetEmployees- Get employeeshrisGetEmployments- Get employmentshrisGetGroups- Get groupshrisGetLegalEntities- Get legal entitieshrisGetLocations- Get work locationshrisGetPerformanceReviewCycles- Get performance review cycleshrisGetPerformanceReviews- Get performance reviewshrisGetTimeOffBalances- Get time off balanceshrisGetTimesheets- Get timesheets
The TypeScript SDK makes API calls using an HTTPClient that wraps the native
Fetch API. This
client is a thin wrapper around fetch and provides the ability to attach hooks
around the request lifecycle that can be used to modify the request or handle
errors and response.
The HTTPClient constructor takes an optional fetcher argument that can be
used to integrate a third-party HTTP client or when writing tests to mock out
the HTTP client and feed in fixtures.
The following example shows how to use the "beforeRequest" hook to to add a
custom header and a timeout to requests and how to use the "requestError" hook
to log errors:
import { Kombo } from "@kombo-api/sdk";
import { HTTPClient } from "@kombo-api/sdk/lib/http";
const httpClient = new HTTPClient({
// fetcher takes a function that has the same signature as native `fetch`.
fetcher: (request) => {
return fetch(request);
}
});
httpClient.addHook("beforeRequest", (request) => {
const nextRequest = new Request(request, {
signal: request.signal || AbortSignal.timeout(5000)
});
nextRequest.headers.set("x-custom-header", "custom value");
return nextRequest;
});
httpClient.addHook("requestError", (error, request) => {
console.group("Request Error");
console.log("Reason:", `${error}`);
console.log("Endpoint:", `${request.method} ${request.url}`);
console.groupEnd();
});
const sdk = new Kombo({ http_client: httpClient });You can setup your SDK to emit debug logs for SDK requests and responses.
You can pass a logger that matches console's interface as an SDK option.
Warning
Beware that debug logging will reveal secrets, like API tokens in headers, in log messages printed to a console or files. It's recommended to use this feature only during local development and not in production.
import { Kombo } from "@kombo-api/sdk";
const sdk = new Kombo({ debug_logger: console });For supported JavaScript runtimes, please consult RUNTIMES.md.
While we value open-source contributions to this SDK, this library is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.