Docs / Data sources / Railz

Railz

Finance and operations

Built when you ask for it

Sync Railz business, invoice, bill, and financial statement 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 Railz connector syncs your accounting data aggregation data into analytics-ready tables in your data warehouse. Pull businesses, invoices, bills, and financial statements from the Railz 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:

  • Businesses
  • Invoices
  • Bills
  • Financial statements

How it gets built

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

What you will need

API key exchanged for a short-lived Bearer token. Sign up for a Railz Dashboard account and generate a Sandbox or Production API key/secret.

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 Railz connector?
Not as a finished connector yet. Ingest builds it from Railz's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Railz 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.

Railz API documentation: https://docs.railz.ai/reference/railz-api

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 ERP teams: SAP, Oracle NetSuite, Microsoft Dynamics 365, Workday, Odoo, Acumatica.

Request Railz