Data & Storage · Integration
CommCare
Add CommCare to your product for your customers, and give your AI agents governed access to it.
CommCare's REST API is scoped to a project space and the project space sits in the path itself, as in /a/{project}/api/v0.5/case/, so credentials and URLs cannot be separated. Authentication is either HTTP Basic with a web user or an API key passed as an ApiKey user:key header, and keys can be pinned to an IP allowlist per user. Case data is not a flat table: each case has a type, an owner id, indices pointing at parent cases and a bag of user-defined case properties that changes as the application is revised. Form submissions come back as JSON derived from XForms, so question paths mirror the form XMLNS and a change to the form changes the shape of what you read. Incremental pulls are far better served by paging the case list with a server-side modified-on cursor than by scheduled exports. fastn holds each project space's credentials, keeps the scoping correct and maintains the connector as API versions move.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own CommCare project space so your product reads cases without a manual data export.
Sync changed case properties into a reporting store using a modified-on cursor rather than a full reload.
Create or close cases from your own workflow so field workers pick them up on their next device sync.
Map form submissions into structured records for a programme monitoring dashboard.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Have an agent report how many open cases of a given type changed this week, with each read audited per tenant.
Let an agent look up a single case and its parent case before a supervisor makes a follow-up decision.
Ask an agent to flag forms submitted with a required question left blank.
Example prompt
How many household cases were modified in the last seven days?
Set up CommCare in 4 steps
- 01Enable the CommCare connector from your fastn dashboard.
- 02Have each customer authorise their own CommCare account, so calls run under their credentials rather than a shared key.
- 03Decide which records, datasets and fields your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the CommCare integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a CommCare integration without building it. Your customers connect their own CommCare account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a CommCare update is not your on-call problem.
- One integration serves your product and your agents. The same governed CommCare connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Snowflake
Airtable
PostgreSQLOften used alongside
Tools the same teams tend to run next to CommCare, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceCommCare integration FAQ
How do I add a CommCare integration to my product?
Enable the CommCare connector in your fastn dashboard, then let each customer authenticate their own CommCare account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no CommCare client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own CommCare account?
Yes. Every connection is scoped to the individual customer, so each authorises their own CommCare account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this CommCare integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Have an agent report how many open cases of a given type changed this week, with each read audited per tenant.
Who maintains the CommCare integration?
fastn does. When CommCare changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the CommCare integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large CommCare reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the CommCare integration?
A common starting point: let a customer connect their own CommCare project space so your product reads cases without a manual data export. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the CommCare integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding CommCare does not change your per-connector cost. You can start free with 3 connected accounts.
Add CommCare to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.