TL;DR Short answer: the best Ashby ETL tools depend on whether you need full snapshots or incremental changes, and on how much of Ashby's built-in analytics you already use. The Ashby API allows 1,000 requests per minute per key and supports sync tokens for incremental reads, but not every connector uses them. Seven Ashby ETL tools compared:
Airbyte Estuary Fivetran Merge Ashby analytics Ashby HRIS integrations Custom code with the Ashby API The Ashby constraint: API keys are scoped per module, so a key missing a read permission silently drops whole streams. Check permissions before your first sync and compare record counts afterwards. Ashby ETL tools and Ashby integrations move candidates, applications, jobs, interviews, feedback and offers out of the Ashby ATS and into a cloud data warehouse , HR system or BI tool. Talent and people analytics teams use them to join hiring data with HRIS, finance and performance data that Ashby does not hold.
Why use Ashby ETL tools if Ashby has built-in analytics? Ashby is known for strong built-in analytics, covering pipeline, conversion, source and interviewer reports inside the Ashby ATS. Teams still move the data out when they need hiring joined with employee records, compensation, performance and finance, or one model across several ATS and HR systems. That needs Ashby data in a warehouse, which is what Ashby ETL tools are for.
How do the Ashby ETL tools compare? Tool Best for Sync method Deployment Pricing model Airbyte Warehouse analytics Full refresh, scheduled Airbyte Cloud, Airbyte Flex, self-hosted Airbyte Core Free self-hosted Core; Cloud volume-based; Pro and Flex capacity-based Estuary Incremental or real-time sync Incremental via sync tokens Cloud, private, BYOC Per GB plus connector instances Fivetran Managed warehouse pipeline Scheduled sync Cloud, hybrid Monthly active rows Merge Unified ATS API for products API calls Cloud Subscription by linked accounts Ashby analytics In-app recruiting analytics Built-in Inside Ashby Included, by plan HRIS integrations Moving hires into an HRIS Event-based Inside Ashby Included, by plan Custom code Exact control Whatever you build Wherever you run it Free, engineering time
Which Ashby ETL tools should you consider? Seven Ashby ETL tools, from warehouse replication to Ashby's own analytics:
1. Airbyte Airbyte is the open-source data connectivity platform for AI and analytics, and among Ashby ETL tools it gives you the most control over where data lands. Its Ashby source connects with an API key and a start date, and replicates applications, candidates, candidate tags, jobs, job postings, offers, interview schedules, feedback forms, departments, locations, sources, users and custom fields. It reads streams concurrently while budgeting against Ashby's limit of 1,000 requests per minute per key, and runs full refresh syncs. For other ELT options, see our guide to ELT tools .
Airbyte has 700+ connectors, and Connector Builder covers niche HR tools a catalogue misses. You can run it in Airbyte Cloud, in your own environment with Airbyte Flex, or self-hosted with Airbyte Core. Ashby is also one of the connectors Airbyte makes available to AI agents through the Airbyte MCP, currently in beta.
Pros Cons Broad coverage of Ashby recruiting objects Full refresh only, no incremental sync Cloud, Flex or self-hosted Core deployment Each stream needs the right module permission Connector Builder for other HR tools Large histories are re-read on each run
2. Estuary Estuary is one of the real-time Ashby ETL tools: its Ashby connector uses API key authentication with scoped access and syncs every resource incrementally using Ashby's sync tokens, then delivers data to Snowflake and other destinations in real time or on a schedule. For warehouse-side options, see our guide to Snowflake ETL tools .
Pros Cons Incremental sync for every resource Per-GB pricing grows with volume Real-time or scheduled delivery Smaller ecosystem than older vendors Private and BYOC deployment options Private and BYOC need annual contracts
3. Fivetran Fivetran is one of the managed Ashby ETL tools: its connector loads Ashby recruiting data into a standard warehouse schema with no pipeline code to maintain. It suits teams already running Fivetran for other sources. Fivetran completed its merger with dbt Labs in June 2026.
Pros Cons Fully managed, with a standard schema Monthly active row pricing No pipeline code to maintain Connector behaviour cannot be modified Same platform as other Fivetran sources Warehouse-only destinations
4. Merge Merge is a unified API platform for product teams: its ATS API normalises candidates, applications, jobs and interviews from Ashby and other applicant tracking systems into one schema. It suits software companies building recruiting integrations for their customers, rather than internal analytics. For other ATS options, see our guides to Greenhouse ETL tools and Workable ETL tools .
Pros Cons One API for many ATS platforms Built for product integrations, not analytics Normalised recruiting models Subscription by linked accounts Handles auth and API changes Less detail than raw Ashby fields
5. Ashby analytics Before choosing Ashby ETL tools, check how far Ashby analytics can take you. Ashby includes built-in reports and dashboards for pipeline, conversion rates, sources, time to hire and interviewer activity, with custom reports on Ashby's own data. It answers most recruiting questions, but cannot join hiring data with HRIS, finance or performance systems.
Pros Cons Strong built-in recruiting analytics Limited to Ashby's own data Custom reports and dashboards Cannot be joined with other systems automatically No pipeline to run Depth depends on your plan
6. Ashby HRIS integrations Ashby integrates natively with HR systems, so hired candidates move into your HRIS without re-typing. These integrations handle the hire-to-onboard handoff, not analytics. If BambooHR is your HRIS, see our guide to BambooHR ETL tools for getting both systems into one warehouse.
Pros Cons Hires flow straight into your HRIS Operational handoff, not analytics Included with Ashby Limited to supported HR systems Less manual data entry No historical recruiting data
7. Custom code with the Ashby API When no Ashby ETL tools fit a narrow need, you can call the API yourself. The Ashby API uses POST requests to named endpoints such as candidate.list and application.list, authenticated with an API key over basic authentication, and list endpoints return sync tokens so later calls fetch only changes. Ashby webhooks notify you of events such as application updates. You own pagination, sync tokens and permissions.
Pros Cons Incremental reads with sync tokens You own pagination, retries and token state Webhooks for recruiting events Per-module API key permissions to manage No licence cost Ongoing maintenance
How does the Ashby API work? The Ashby API is RPC-style: every call is a POST to a named endpoint, such as candidate.list, application.info or job.list. You authenticate with an API key sent through basic authentication, and each key is granted read or write permissions per module, such as candidates, jobs or offers. List endpoints return a sync token, so the next call returns only records that changed, and the default limit is 1,000 requests per minute per key.
How do you get Ashby data into Snowflake or BigQuery? Most of these tools load either warehouse. Create a dedicated Ashby API key with read access to the modules you need, including Organization, then replicate with Airbyte, Estuary or Fivetran and compare record counts with Ashby. Load your HRIS into the same warehouse so hires join to employee records; see our guide to Google Sheets ETL tools for spreadsheet reporting on smaller teams.
What should you check before syncing Ashby? Whichever Ashby ETL tools you choose, most problems come from key permissions, sync mode and candidate privacy. Check these first:
Module permissions: Ashby API keys are scoped per module. Missing a read permission drops a stream without an obvious error, and Organization read is needed for connection checks.Full refresh or incremental: some connectors re-read everything on each run, while others use sync tokens. Choose based on your data volume and freshness needs.Rate limits: the default limit is 1,000 requests per minute per key. Use a separate key per integration so one tool cannot starve another.Start dates: a start date limits historical data on some streams. Set it early enough for the trends you want to analyse.Candidate privacy: candidate records include personal details, resumes and feedback. Respect deletion requests and restrict warehouse access.Webhooks: Ashby webhooks signal events but do not replay history. Pair them with scheduled syncs.The Ashby API exposes recruiting data, including:
Candidates and applications: people, sources, tags, stages and outcomes. Jobs and job postings: open roles, departments, locations and published listings. Interviews and feedback: schedules, feedback forms and interviewer submissions. Offers: offer details, approvals and status. Users: recruiters, coordinators and hiring managers. Custom fields and archive reasons: company-specific attributes and why candidates were archived. How do you start pulling data from Ashby? If you decide to test Airbyte, setting up an Ashby pipeline takes three steps.
Step 1: Set up Ashby as a source In Ashby, open Admin, then API Keys, and create a key with read permissions for Organization and every module you want to sync. In Airbyte, open Sources, choose New source, select Ashby and enter the API key and a start date.
Step 2: Set up a destination Pick where your Ashby data should land: a warehouse such as Snowflake, BigQuery or Databricks, a database, or a lake, with access restricted to talent and HR users.
Step 3: Configure the connection Select candidates, applications, jobs, offers and interview schedules, run the first sync, and compare record counts with Ashby. The process is the same whether you start with Airbyte Cloud or run self-hosted Airbyte Core .
Which Ashby ETL tool should you choose? The right Ashby ETL tools depend on freshness and what else lives in your warehouse. For Ashby next to your HRIS and other sources, use Airbyte for deployment control, Estuary for incremental or real-time sync, or Fivetran for a managed connector. Merge suits product teams building ATS integrations, the HRIS integrations handle new hires, and Ashby analytics covers most in-app recruiting questions.
For a wider view of the market, see our guide to the best data integration tools .
Replicate Ashby with Airbyte Airbyte is the open-source data connectivity platform for AI and analytics. Replicate Ashby candidates, applications and offers into the warehouse you choose, next to your HRIS and 700+ other sources, in Airbyte Cloud, in your own environment with Airbyte Flex, or self-hosted with Airbyte Core.
Try Airbyte Cloud free for 14 days or talk to our team .
Frequently Asked Questions (FAQs) 1. What are the best Ashby ETL tools? The best Ashby ETL tools depend on your needs. Airbyte, Estuary and Fivetran suit warehouse analytics, Merge suits product integrations, Ashby's HRIS integrations handle new hires, and Ashby analytics covers in-app reporting.
2. What is the Ashby API rate limit? Ashby allows 1,000 API requests per minute per API key by default. Use a separate key for each integration so one tool cannot use up another's budget.
3. How do you authenticate with the Ashby API? Create an API key in Ashby's admin settings, grant read or write permissions per module, and send the key with basic authentication on each POST request.
4. Does the Ashby API support incremental sync? Yes. Ashby list endpoints return sync tokens, so later requests fetch only changed records. Some connectors use them, while others run full refresh syncs.
5. Does Ashby support webhooks? Yes. Ashby webhooks notify another system about events such as application changes. They do not replay history, so pair them with scheduled syncs.
Suggested reads Greenhouse ETL Tools
Workable ETL Tools
BambooHR ETL Tools
Snowflake ETL Tools
.webp)