Docs / Data sources / Leave Dates

Leave Dates

Business software

Built when you ask for it

Sync Leave Dates leave, employment, department, and allowance data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Leave Dates connector syncs your leave and absence-management data into analytics-ready tables in your data warehouse. Pull leaves, employments, departments, and allowances from the Leave Dates API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Leaves
  • Employments
  • Departments
  • Allowances

How it gets built

  1. Choose Leave Dates when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Leave Dates's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Leave Dates itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

Bearer token (personal access token). Sent as an Authorization: Bearer header; exact in-app steps to generate the token aren't published in the public docs.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Leave Dates connector?
Not as a finished connector yet. Ingest builds it from Leave Dates's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Leave Dates data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Leave Dates API documentation: https://api.leavedates.com/documentation

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Leave Dates