Stop re-typing the same data twice.
If your team already keeps a separate system of record, your HMIS, a reporting portal, a BI dashboard, Forzara's API lets you pull your organization's own roster, milestone, and meeting data out automatically instead of a coordinator re-entering it by hand.
Already a Forzara org? An admin can generate a key from Admin Panel → API Access. Already building against it? See the API Reference →
- Read-only — nothing an API key touches can ever change your data
- Every key is locked to your organization, and to only the data you choose to expose
- Case notes are never exposed, only status
- Every request is rate-limited and logged
What programs actually use it for
Five real reasons an org would pull data out of Forzara automatically, instead of leaving it as something only staff who log in can see.
Feed your own HMIS
If your program reports into a CoC-designated HMIS, a nightly pull of roster and milestone data means your case managers stop re-entering the same enrollment and progress info in two places.
Auto-populate grant reports
GPRA, JAG, and CSBG reports need participant counts and milestone completions within a date range. Pull that straight into your reporting template instead of re-keying it from Forzara by hand.
Roll into your own dashboard
Multi-program agencies already running Power BI, Tableau, or similar can bring Forzara's numbers in alongside every other program instead of leaving them in a separate silo.
Document contact frequency
Some grants require a minimum number of case-management contacts per participant per month. Meeting data (scheduled, completed, canceled) is that log, ready to pull instead of counted by hand.
Warm handoffs with a partner agency
When a participant is shared between two agencies, a partner's own system can check enrollment status and current coach without logging into Forzara, when your organization decides to share it.
You choose what a key can see.
Case notes are never one of the options.
Every key belongs to your organization, not a person, and starts with zero access. An admin turns on only the resources it needs.
Roster
Participant/staff name, email, role, status, and assigned coach.
Milestones
Completion and submission status only. Case notes and review notes are never selected by the API, at the database query level.
Meetings
Milestone review and follow-up meeting schedule, status, and outcome.
This isn't a filing connection. The API pulls your organization's own data out of Forzara, it does not push anything into your state's reporting portal, your CoC's HMIS platform, DOJ's PMT, or SAMHSA's SPARS. Getting the data into one of those systems is still your team's (or your HMIS vendor's) work, this just means that work can start from an automated export instead of someone re-typing it.
Not self-serve, on purpose.
Tell us what you're connecting to
Your HMIS, a BI tool, an internal reporting script, whatever you're feeding. We'll confirm the resources and scopes it actually needs.
We turn it on for your org
An admin generates a scoped key from Admin Panel → API Access. The key works immediately, limited to the resources you asked for.
Your side pulls the data
A nightly cron job, a Zapier/Make step, or a script your team already runs, GET requests, JSON responses, nothing to install on our end.
Have a system you're already re-typing Forzara data into?
Tell us what you're connecting to. We'll confirm it's a fit and get a scoped key turned on for your org.