Tyler Munis
Government
Sync Munis general ledger, budgets and purchasing. 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 Tyler Munis connector syncs general ledger, budgets, purchase orders into analytics-ready tables in your data warehouse. Ingest builds it on request, 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:
- General ledger
- Budgets
- Purchase orders
How it gets built
- Choose Tyler Munis when you set up a pipeline, with the warehouse it goes to and a schedule.
- Ingest reads Tyler Munis's documentation, and you choose the tables you want.
- Ingest builds the connector and tests it against Tyler Munis itself.
- A person at Ingest reviews and publishes it, and your pipeline starts on its own.
What you will need
API credentials issued by the vendor. Tyler Munis gives API access to its customers on request. Ask your Tyler Munis administrator or account manager for read-only API credentials; Ingest tells you exactly which values it needs when it builds the connector.
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 Tyler Munis connector?
- Not as a finished connector yet. Ingest builds it from Tyler Munis's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
- Which warehouses can Tyler Munis data go to?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, 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.
Tyler Munis API documentation: https://www.tylertech.com/products/enterprise-erp
Where this would land, and what else connects
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, ObsessionDB, MySQL / generic SQL, Snowflake.
Other sources Ingest connects for government teams: Abilene TX 311, Albany NY 311, Ann Arbor MI 311, Anne Arundel County MD 311, Auburn WA 311, Aurora IL 311.