HawkSoft connection evaluation
Decla for HawkSoft
Evaluate a HawkSoft task by separating provider API access, your agency’s enabled scopes and the operations Decla has actually verified. HawkSoft’s public documentation describes what an approved integration can do; it does not prove a Decla action in your agency.
Talk through your agency's workflows
See Decla with your team
Book a demo to walk through how Decla fits the day-to-day work your agency team handles, and where to start.
Discuss your HawkSoft taskOn this page
Public docs, controlled access
HawkSoft publishes Partner API documentation, including V4.0. Public documentation is separate from permission to operate on an agency’s data.
API access requires provider partner approval and agency opt-in. The overview documents partner authentication; a valid credential alone does not establish access to a particular agency. Additional scopes must be enabled for the integration and opted into by the agency.
Provider documentation checked October 6, 2026. Exact Decla lookup, write and agency permission evidence has not been verified for this page. No subscription price, setup duration, partner-directory status or blanket policy-editing support is asserted.
Sources
- HawkSoft Partner API documentation — accessed
- HawkSoft API overview — accessed
- HawkSoft data scopes — accessed
Follow the access boundary
Provider approval
Confirm the actual integration’s provider approval and interface/version. A website logo or directory entry is not evidence of a completed task.
Agency opt-in
Confirm the agency subscribed to the integration and which available scopes it enabled. Keep access and operation permissions separate.
Returned data
Check the requested includes and any denied data before treating a source record as complete.
Action and verification
Identify the agency reviewer, permitted action, resulting artifact and follow-up evidence. Keep queued work separate from a persisted log.
Provider scope is not Decla operation proof
| Task | HawkSoft documented boundary | Decla evidence |
|---|---|---|
| Client/policy lookup | Client read scope; policy-number search is exact-match. | Not verified for this page. |
| Log notes, attachments and tasks | Separate create-log-attachment-task scope. | Not verified for this page. |
| Invoices and payments | Accounting scope; invoice includes require agency opt-in. | Not verified for this page. |
| Prospect creation | client-create covers prospects with limited policy details. | Not verified; not unrestricted policy editing. |
Sources
- HawkSoft data scopes — accessed
- HawkSoft V4.0 API — accessed
A successful lookup can still omit a source
V4 requests specify version=4.0. Client reads can request selected includes. If requested data is not permitted, the call can succeed with allowed data while a Denied response header identifies withheld includes. Missing invoice data is therefore not proof that no invoice exists.
Illustrative example using synthetic data: an exact policy-number lookup for SYN-065 returns a matching record, but Invoices is denied. A reviewer can use the available policy context and record the invoice source gap; the missing amount stays unverified. No real API call, agency permission or Decla result is represented.
Sources
Created and queued are different outcomes
| Observed response scenario | Meaning | Next record |
|---|---|---|
| Read succeeds; Invoices denied | Allowed data returned; requested invoice source unavailable. | Record the gap; do not infer a zero balance. |
| Log response 200 | Provider documents the log as created. | Verify the intended client, content and record before closing the task. |
| Log response 202 | Provider saved the request for creation when the agency reconnects to the cloud. | Keep pending; assign follow-up and verify creation later. |
| Permission failure | Agency access or endpoint permission is unavailable. | Stop the affected action; resolve access through the approved owner. |
Sources
- HawkSoft V4.0: log note responses — accessed
Bring one bounded task to the discussion
For example, ask about gathering a policy record and preparing a reviewed status note. Specify the agency, source fields, reviewer and intended log destination. Require a dated demonstration of the exact Decla operation before treating it as available.
The synthetic deferred-write branch ends pending, not completed: retain the request reference and next owner, then verify actual creation after reconnection. Do not submit a duplicate simply because creation is deferred; confirm the integration’s retry behavior first. No retry or readback mechanism is claimed for Decla here.
Reading data or creating a documentation log does not establish authority to change coverage, issue a certificate or edit every policy field. Those actions need their own scope and operational evidence.
Frequently asked questions
Can AI process policy endorsements and enter them in HawkSoft?
Evaluate a HawkSoft task by separating provider API access, your agency’s enabled scopes and the operations Decla has actually verified. HawkSoft’s API doesn’t allow coverage changes on existing policies, so in that case Decla prepares the work and a person finishes it in HawkSoft.
What is Decla?
Decla is AI software for independent insurance agencies and brokerages. It connects to your AMS, email and carrier portals and does back-office work inside them. Your team reviews the work before it goes out.