HawkSoft APIConnect HawkSoft without building on its API
HawkSoft has a Partner API (REST). Only approved API partners get credentials, and each agency has to opt in to share its data through the HawkSoft Marketplace before a partner can reach it. If you're reading the docs because you need HawkSoft to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across HawkSoft and your other tools.
- APIREST (JSON), Partner API
- AuthPartner client ID and secret
- AccessApproved partners only
What the HawkSoft API gives you
- Type
- REST (JSON), Partner API
- Authentication
- Partner client ID and secret
- Who can get access
- Only approved API partners get credentials, and each agency has to opt in to share its data through the HawkSoft Marketplace before a partner can reach it.
- What it covers
- Agencies, offices and clients (people, contacts, claims, policies, invoices), a changed-clients sync, and writing back log notes and attachments.
- Limits
- Client reads are batched at up to 200 per request.
- Worth knowing
- Writing back is limited to documentation such as log notes and attachments.
Official docs: partner.hawksoft.app. Checked September 2026. Vendors change access terms, so confirm with HawkSoft before you build.
Building on the HawkSoft API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get HawkSoft credentials, and manage tokens and refreshes. | Connect your HawkSoft account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the HawkSoft task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting HawkSoft work off someone's desk, the build is the slow part.
What teams usually want the HawkSoft API for
New business intake
Caddi turns inbound applications and email into the matching HawkSoft client and policy records.
Renewal & document workflows
Caddi prepares renewals and files documents to the right HawkSoft record on schedule.
HawkSoft API questions
Does HawkSoft have an API?
Yes. HawkSoft has a Partner API (REST), authenticated with Partner client ID and secret. The official documentation is at https://partner.hawksoft.app/.
How do I get access to the HawkSoft API?
Only approved API partners get credentials, and each agency has to opt in to share its data through the HawkSoft Marketplace before a partner can reach it.
Does the HawkSoft API have rate limits?
Client reads are batched at up to 200 per request.
Can I connect HawkSoft to my other tools without writing code against its API?
Yes. With Caddi you show the HawkSoft task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across HawkSoft and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate HawkSoft with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for HawkSoft is reviewed before it runs in production, and every run is logged.
Connect HawkSoft without the build.
Drop your work email and pick a time. We'll show you Caddi running your HawkSoft workflow end to end.