Highlights

• ✍️ Enable and Disable Integrations via API: You can now programmatically manage the status of your integrations with the new PUT /integrations/{integration_id}/enabled endpoint. This provides greater control and automation for managing your customers' connections.

Other Updates

• 🛟 Support Portal Link: We've added a direct link to our Support Portal in the dashboard sidebar for easier access to help.
• 📡 Dashboard: The "Incoming Request" tab in the interaction logs is now visible to all users by default, providing more debugging context for every interaction.
• 👻 Komboman API Explorer: The button to delete a history entry in our dashboard's API explorer is now available to all users, making it easier to manage your test requests.
• 🔄 Sync Reliability: We've improved the logic for resetting data expiration status for partially failed syncs, ensuring data freshness is more accurately reflected.
• 🕸️ Webhook Reliability: We've made our webhook system more robust to ensure notifications are definitely delivered.

Highlights

• 🔐 Expiring API Keys by Default: To enhance security, all newly generated API keys will now expire after 30 days by default. You can still create non-expiring keys for production use cases by explicitly acknowledging the security implications in the dashboard.
• 🔎 Flexible API Filtering: We've introduced a new query parameter, ignore_unsupported_filters, to all model GET endpoints. When set to true, our API will ignore any filters not supported by the specific integration, preventing errors and allowing you to use a single filter set across all providers.
• 🕰️ Extended Audit Log Retention: The retention period for audit logs has been extended up to 3 years for customers on enterprise plans, providing a longer history of activities for compliance and security reviews.

Other Updates

• 🕵️ API Key User Agent Tracking: We now track the User Agent for each API call, which is visible in the dashboard. This helps you easily identify how your keys are being used, for instance, via our SDKs, Postman, or your application's backend.
• 📊 Dashboard Improvements: We've rolled out several enhancements to the dashboard, including a more informative coverage grid with descriptions for each capability and an improved, denser UI for viewing API request logs.

Highlights

• 🔐 Improved Partner Credential Management: We've overhauled the partner credentials management in the dashboard. You can now manage different versions (revisions) of your credentials, assign labels for clarity, and view which integrations are using a specific credential set. This makes it easier to rotate keys and manage credentials at scale.
• 💪 More Resilient OAuth Connections: We've improved our OAuth token refresh mechanism. We expect to decrease the number of invalid credentials caused by errors during token refreshing.

Other Updates

• 🖥️ Dashboard Improvements: We've rolled out several enhancements to the dashboard. The logs viewer now has better auto-scrolling behavior and a "Back to top" button. We've also reduced unnecessary network requests in inactive tabs to improve performance.
• ⚖️ Integration Enablement Flow: To ensure you are fully aware of an integration's capabilities and limitations, you must now visit the integration's detail page in the dashboard before enabling it.

Highlights

• 🔎 Redesigned Logs for Easier Debugging: We've completely overhauled the Logs page in the dashboard. You can now view the exact data that caused a parsing error and replay failed requests directly in our API explorer, making it much faster to debug integration issues.
• ⚡️ Faster Syncs with Optimized Filtering: We've significantly improved the performance of requests using the `updated_after` filter. This change speeds up incremental syncs for integrations with large datasets.
• 🐛 SDK Pagination Fixed: We've resolved an issue in our SDKs where the pagination cursor for the next page of results was not being extracted correctly. Please update to the latest version of the SDK to benefit from this fix.

Other Updates

• 🔌 Reconnect from Dashboard: You can now trigger a reconnection for an integration with invalid credentials directly from the Kombo dashboard, simplifying the recovery process for your customers.

Highlights

• 🗓️ New data_expired_at Field: The integration details endpoint now includes a data_expired_at timestamp. This field indicates when an integration's data has become stale, for example, after your customer updates their filter settings or scope config, and is automatically cleared after a successful sync.
• 🔎 Major Logs Page Upgrade: We've significantly enhanced the logs page in the dashboard. You can now use multi-select filters for status, type, error code, and integrations, making it much easier to drill down into specific interactions. We've also added fuzzy search to dropdowns and new filters like "Uncategorized Errors".

Highlights

• 📣 Deprecation: `remote-event-received` Webhook Removed: As previously announced, the legacy `remote-event-received` webhook has been fully removed. Please ensure you have migrated to our `data-changed` webhook, which provides more granular and reliable notifications for data updates.
• 🔐 New Webhook Secret Regeneration: For enhanced security, you can now regenerate your webhook signing secret directly from the Kombo dashboard. This allows you to easily rotate keys as part of your security protocol.
• 💅 Major Dashboard UI Upgrade: We've completely overhauled the select and filter components across the dashboard. This brings a much-improved user experience with searchable, grouped, and multi-select options, making it faster to navigate and find the information you need.

Other Updates

• ⏰ Timestamps in Logs: All entries in the request logs view now include a timestamp, making it easier to correlate events and debug issues.
• 📊 Enhanced Log Filtering: You can now filter logs by more properties.
• 🔗 Improved Webhook Data Visibility: The integrations list in your dashboard now shows when data was last updated by a webhook, giving you a more complete picture of data freshness alongside regular syncs.
• 🛠️ Improved Webhook Coverage Reporting: We've improved how we communicate the exact coverage of webhooks for each integration, providing more clarity on which events will trigger a notification.

Highlights

• 📣 Action Coverage in API: The GET /v1/integrations/{integration_id} and GET /v1/tools endpoints now return detailed information about supported write actions, including which input fields are available for each action. This allows you to programmatically discover the full capabilities of an integration.
• 📜 Improved Developer Dashboard Logs: We've overhauled the logs view in your dashboard. It now features a cleaner UI with markdown formatting for better readability and more helpful error messages to accelerate debugging.
• Deprecation Notice: The sync-finished webhook is being deprecated. We recommend migrating to the more efficient data-changed webhook to receive real-time notifications for data updates.

Highlights

• 📣 Official TypeScript & Python SDKs: We've launched official SDKs for TypeScript and Python to make integrating with Kombo even faster. Our documentation has been updated with code samples for both languages directly on the endpoint pages to help you get started.
• 🔎 Revamped Logs Filtering: The Logs page in your dashboard has been significantly improved with powerful new filtering capabilities. You can now filter interactions by integration, action type, status, and other tags, making debugging much faster and more intuitive.
• 🌍 “Open in Remote System” Links in Data Explorer: You can now jump directly from a record in the Kombo Data Explorer to the corresponding page in your customer's HR system. These new deep links are available for candidates, jobs, and applications across many integrations.

Other Updates

• 💅 Dashboard response viewers in the Data Explorer and API explorer now feature syntax highlighting and auto-formatting for JSON and XML, improving readability.
• 📋 In the logs viewer, the “Copy” button for request bodies now copies the full, untruncated content, making it easier to work with large payloads.
• 🏷️ The integration catalog now more clearly indicates which integrations require a custom plan.
• ⚡️ We've improved our remapping engine to better handle structured data (like addresses) where all fields are null.

We're excited to share that Kombo now provides official server-side SDKs for TypeScript/JavaScript and Python! 🎉

Why use our SDKs?

Our official SDKs are the recommended way to implement Kombo and offer several key advantages:

• ✨ Ergonomic and type-safe API interactions
• 🔄 Always up to date with the latest Kombo API changes
• 💡 Auto-completion and detailed types for inputs and outputs
• 🛡️ Avoid common pitfalls with built-in best practices

Get Started

TypeScript/JavaScript

npm install @kombo-api/sdk

📦 npm | 💻 GitHub

Python

pip install kombo

📦 PyPI | 💻 GitHub

Example Usage

import { Kombo } from '@kombo-api/sdk'

const kombo = new Kombo({
  api_key: process.env.KOMBO_API_KEY,
  integration_id: 'workday:HWUTwvyx2wLoSUHphiWVrp28',
})

const result = await kombo.hris.getEmployees()

Migrating from Custom Code?

If you're currently using custom code or self-built solutions to interact with Kombo, now is a great time to migrate! Our SDKs will save you time and reduce maintenance overhead. We've created an LLM-friendly migration prompt to help automate the process. Check out our documentation for details.

More server-side SDKs are planned. Have a specific tech stack in mind? Please reach out!

Highlights

• Improved Rate Limit Handling: We've enhanced our system to more accurately parse Retry-After and X-RateLimit-Reset headers from various providers. This leads to more reliable and resilient integrations by respecting provider rate limits more effectively.
• More Actionable API Error Messages: We've significantly improved validation error messages. When you provide invalid data for fields that accept multiple types (unions), the error message will now clearly detail why each type failed validation, making it much easier to debug your requests.

Other Updates

• In the dashboard, request and response logs are now displayed in a syntax-highlighted code viewer for improved readability.