Source connector
Ashby connector
Ashby integration for databases, warehouses and BI tools
Applicant tracking and recruiting analytics. Datrise captures Ashby entities such as candidates, applications, jobs, interviews, offers and interview feedback, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.
The Ashby API (RPC-style POST endpoints) authenticates with HTTP Basic, incremental runs key on syncToken.
Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `ashby_candidates`) with a schema derived from the Ashby API rather than a flattened CSV, in any of the 43 supported destinations.
Datrise is in early access: pick a destination below to open the Ashby pipeline page, and join the waitlist to get the Ashby connector with guided onboarding.
What Ashby data Datrise extracts
Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.
| Object | Landing table | Sync mode |
|---|---|---|
| candidates | ashby_candidates | Upsert by primary key, incremental on updated-at |
| applications | ashby_applications | Upsert by primary key, incremental on updated-at |
| jobs | ashby_jobs | Append-only, incremental by timestamp |
| interviews | ashby_interviews | Upsert by primary key, incremental on updated-at |
| offers | ashby_offers | Upsert by primary key, incremental on updated-at |
| interview feedback | ashby_interview_feedback | Upsert by primary key, incremental on updated-at |
Ashby API: setup facts for the connector
Verified against the vendor documentation on 2026-10-26. Unknown values are left blank rather than guessed.
| API | Ashby API (RPC-style POST endpoints) |
|---|---|
| Authentication | HTTP Basic — HTTP Basic with the API key as the username and an empty password; keys carry per-module read/write permissions. |
| Pagination | cursor — List endpoints return `nextCursor` and `moreDataAvailable`; send `nextCursor` back as `cursor`, with an optional `limit`. |
| Rate limit | Not published |
| Incremental cursor | syncToken — Only endpoints whose request schema includes `syncToken` support incremental sync; the final page returns a new token to store. |
| Webhooks | Yes — Webhooks configured in Ashby (signed with an `Ashby-Signature` header when a secret is set) |
| Bulk export | Not published |
| Deletes detectable | Not published |
What bites when replicating Ashby
- An incremental sync is limited to 100 pages; beyond that the API returns `incremental_sync_too_large` and you must discard the `syncToken` and run a full sync.
- `nextCursor` and `syncToken` both expire after 14 days (`next_cursor_expired`, `sync_token_expired`); run an incremental sync at least weekly.
- A wrong or deactivated key returns 403, and a key without module permission returns 403 `missing_endpoint_permission`.
- report.synchronous and report.generate are limited to 15 requests per minute per organization with 3 concurrent report operations; no general limit is published.
Popular destinations for Ashby
Choose a destination below to open the ready pipeline page.
- AAirtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline - AAmazon Athena
Serverless SQL over S3 data lake tables.
View pipeline - AAmazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline - AAmazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline - AAmazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline - AAmazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline - AApache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline - AAzure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline - AAzure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline
Ashby connector FAQ
- What Ashby data does the connector extract?
- 6 objects: candidates, applications, jobs, interviews, offers and interview feedback. Each lands in its own table with types preserved; history-style objects (1: jobs) load as append-only streams.
- Is the Ashby integration incremental?
- Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
- Where can I load Ashby data?
- Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Ashby → destination pair has its own page with the object-to-table mapping.
Related sources
Other sources in the same category, each with its own connector page.
Early access
Launch your Ashby pipeline with guided onboarding
Join the waitlist to get priority access for Ashby integrations with guided setup, schema-aware mapping, and production-grade incremental sync.