REST endpoints, JWT scopes, and webhooks.
Technical Integration API documentation for evaluators — credentials, scopes, endpoints, events, webhooks, and AI-agent patterns. Included with your subscription.
Open API
Connect your stack on your terms — included, not upsold.
Structured agency data across CRM, pipeline, comms, renewals, and billing means integrations actually work instead of stitching exports and Zapier zaps.
Explore the Integration API ↓Integration API
A real REST API — built for AI agents and automations.
VentFlow includes a JWT-scoped Integration API with your subscription — not a Zapier tax or an enterprise upsell. External utilities, custom scripts, and AI agents can read and write agency data through the same structured model your producers use in the portal.
Contacts, pipeline deals, communications, billing, marketing content, and automation events — all addressable with scoped credentials and short-lived access tokens.
Integration credentials are provisioned during onboarding or by request — your walkthrough covers scopes, security, and what to connect first.
Auth flow
- 1.Your VentFlow team creates an Integration Client and credential in your account — scoped to only what you need.
- 2.Your utility exchanges client_id + client_secret for a 15-minute Bearer token.
- 3.Call REST endpoints or register webhooks — each route enforces the scopes on that credential.
Granular permissions — nothing extra.
Every credential gets an explicit scope list. Endpoints return 403 with missing_scopes when a token lacks access — so agents and automations stay least-privilege.
CRM & pipeline
Contacts, deals, pipelines, stages, internal forms, and claims.
Communications
Read logged SMS/MMS and send messages with wallet debit.
Marketing content
Blog drafts, scheduling, social posts, and media uploads.
Billing
Read-only invoice list and detail — no payment mutations via JWT.
Automation
Poll canonical events or register signed outbound webhooks.
Structured agency data — addressable by code.
One data model across CRM, pipeline, comms, renewals, billing, and marketing. Integrations work because the platform was built API-first — not exported as an afterthought.
- POST /api/integrations/auth/token — client credentials → JWT
- GET/POST /api/integrations/contacts — CRM records
- GET/POST /api/integrations/pipelines/{id}/deals — pipeline deals
- GET /api/integrations/events — poll deal, contact, form, and alert events
- POST /api/integrations/webhooks/endpoints — HMAC-signed outbound delivery
- POST /api/integrations/blog-posts — create and schedule content
- POST /api/integrations/comms/sms — send SMS/MMS from automations
POST /api/integrations/auth/token
Content-Type: application/json
{
"client_id": "vfd_int_...",
"client_secret": "vfd_secret_..."
}
→ 200 OK
{
"access_token": "eyJhbGciOiJIUzI1NiIs...",
"token_type": "Bearer",
"expires_in": 900
}
GET /api/integrations/contacts?limit=25
Authorization: Bearer eyJhbGciOiJIUzI1NiIs...Workflows your AMS vendor won't build.
These are representative patterns — not a closed list. If your agent can hold a JWT and call REST, it can operate on real insurance workflow data.
Pre-call brief agent
Read contact history and recent comms before a producer dials — summarize timeline context from structured data, not inbox scraping.
contacts:read · comms:read
Speed-to-lead router
Subscribe to form.submission.created webhooks, create or update deals, and assign pipeline stages according to the configured workflow.
webhooks:write · deals:write · internal_forms:read
Stage-change automations
React to signed deal.stage_changed events — notify carriers, create tasks, or push context to external systems your AMS won't connect.
webhooks:write · deals:read
Renewal & TAT watchdog
Poll performance.tat_threshold_* events or deal alerts to flag at-risk renewals and stale pipeline stages before month-end.
events:read · deals:read
Content publishing agent
Draft blog posts, upload hero images, and schedule social — with VentFlow content-service approvals still running inside the portal when enabled.
blogs:create · social:create · media:upload
Transactional email dispatch
Send branded or raw HTML email from external workflows — with delivery receipts for audit and billing.
dispatch:email
Real-time when you need it — polling when you don't.
Poll GET /api/integrations/events for canonical JSON events — deal stage changes, new contacts, form submissions, billing alerts, performance thresholds, and more.
Or register outbound webhooks with HMAC signatures so your agent or automation platform receives verified payloads at your URL. Event filters respect the read scopes on your credential — no silent overscoping.
- 35+ AGP outbound event types — deals, contacts, comms, billing, claims, calendar, tasks
- Signed delivery with rotatable secrets — same infrastructure as portal outbound automations
- Per-account markdown context bundle available for AI tooling (events:read credential)
Ready to simplify the stack?
Book a walkthrough. We'll map what your agency uses today, what VentFlow can consolidate, what should remain in place, and how the systems can work together.
Book a walkthrough