A Church Management Software API for Ekkli: In Development

If you're the person a church leans on to make its systems talk to each other, here's the honest answer up front: Ekkli does not have a public church management software API yet. There's no key to request, no endpoint to call, and no way today to have Ekkli push or pull data automatically to another system. This page exists so you don't spend an afternoon hunting for docs that aren't there, so you know which church software already offers API access for developers if you need it now, and so you can tell us it matters if it does.

What "public API" would even mean here

For a church's tech-savvy volunteer or a network's IT person, "API" usually means one specific, practical thing: a documented, supported way to get data in and out of Ekkli programmatically — member records syncing to another CRM, giving totals feeding an accounting tool, event data flowing to a separate calendar system, or a custom internal dashboard pulling live numbers instead of someone exporting a CSV by hand once a month. That's the gap this page is about. It is not about whether Ekkli can hold your church's data well — it does — it's specifically about whether a third-party system can talk to Ekkli's data automatically, without a person in the loop. Today, it can't.

What exists instead, right now

To be clear about what you actually have to work with today: Ekkli's own features cover most of what a church needs without a separate integration — worship presentation, a church website with a member portal, an admin-facing member management database, rotas, and event registration all live under one login already, which is a large part of why churches move to Ekkli in the first place — fewer systems to connect, not more. Where you do need data out of Ekkli today, that's a manual step (CSV export, for instance), not an automated one. We're not going to pretend that's the same thing as an API, or dress up a manual export as an "integration feature" — it isn't, and a tech volunteer evaluating this deserves a straight answer rather than a marketing rebrand of a limitation.

Church software that does have an API today

If an integration genuinely can't wait, it's worth knowing which church management platforms already ship documented public API access — useful context whether or not you end up switching anything. Elvanto publishes an API covering people, volunteers, groups, services, and events, so a connected system can read and write core church records directly rather than through an export. ChurchTools goes further still, with a published catalog of more than 800 API endpoints included at no extra cost. FellowshipOne (F1) offers a REST API that's free to use for churches and qualified partners building integrations on top of it. (ChurchSuite, IconCMO, and Text In Church also offer some form of API or open data access, if you want to widen the search.) None of this is a knock on where Ekkli is today — these are established platforms that built church software API access for developers because enough of their customers asked for it over enough years to justify the engineering. Ekkli's current bet is that most churches need fewer connected systems, not more, which is why worship, website, members, and events already live under one login instead of five. But if your church's situation genuinely calls for programmatic church software integrations right now, one of the platforms above is a reasonable place to look — and if the missing API is the one thing otherwise holding up a move to Ekkli, read on.

Why we're telling you this is actually planned, not just a wish

We separate "genuinely on the roadmap" from "sounds nice, no evidence" pretty strictly internally, and a public API is in the first category: it's a registered capability in Ekkli's own product configuration, held distinct from features with no groundwork behind them at all. That's a meaningfully different signal from a feature we've merely talked about. What it is not is a commitment to a specific API style, a specific set of endpoints, or a specific quarter — none of those decisions have been made yet, and we'd rather say that plainly than invent a REST-vs-GraphQL answer or a launch window just to sound further along than we are.

What to do if this is blocking you

If a missing API is genuinely the thing standing between your church or network and switching to Ekkli, tell us. Describe the integration you actually need — which system, what data, one-way or two-way, how often — through our contact page. We don't have a formal developer waitlist or an early-access program to offer you today, so we won't pretend one exists; what we can promise is that a specific, real integration need from an actual church carries more weight in shaping this than a generic feature request does, and someone will read it.

This page is maintained by the Ekkli team and reflects the product's actual state as of publication, not an aspiration. If a public API ships in the future, this page will be rewritten to describe what was actually built, not what was originally planned — check back, or contact us to ask directly.