document automation for US MGAs, wholesale brokers and program administrators
Three building blocks turn the policy data in your PAS, AMS or rater into insurance documents: the PDF forms you already use, documents that grow with the data, and workflow rules that choose what goes in the packet.
Static PDF
Upload the binder, the carrier form or the ACORD form your organization is licensed or authorized to use. Place fields once, and every render fills the same boxes from the policy data. The layout, form number and edition date never change.
How static PDF templates workDynamic document
Quote letters, declarations and schedules are written once in the editor. A table grows with the coverages you send, and a paragraph appears only when the data calls for it.
How dynamic documents workWorkflow
Put the documents behind one set of data. Each can carry a rule your team writes, like a state or a coverage. Change Florida to Texas and the Texas notice takes the Florida notice's place.
How conditional workflows workpolicy issuance
Declarations, coverage forms, state notices and endorsements, each included by a rule your team configured, then merged into one policy packet.
Explore insurance policy packet automation for US MGAscertificates of insurance
Map the ACORD 25 your organization is licensed or authorized to use once. Each certificate of insurance then fills from the policy, insured and holder data you send.
Automate ACORD 25 insurance certificate creation from policy dataquote and bind
Once a quote is approved in your PAS or rater, send the data once and get back the quote letter, the binder, the schedule and the forms your rules call for.
See the quote-to-binder document workflowPAS, AMS, rater or spreadsheet
The document layer beside it
from your PAS, AMS or rater
Your system posts JSON to a workflow and gets the packet back, or a signed webhook when it is ready.
from a person
A producer, underwriter or insured fills the workflow's form in the browser, and signs where a document asks for a signature.
inside your portal
A single template's form, such as a certificate request, in an iframe on your own site, allowed only on the origins you list.
from an export
No integration yet? A script can post rows from a spreadsheet or a report to the same API.
for the engineer wiring it up
?async=true, get a 202 now and a signed workflow.run.completed webhook later.curl -X POST https://api.mezdoc.com/api/v1/workflows/policy_packet/runs \
-H "Authorization: Bearer sk_test_..." \
-H "Content-Type: application/json" \
-d '{ "data": { "insured_name": "Harbor Point LLC",
"state": "FL", "product": "GL",
"additional_insured": true } }'
# 200 OK: run_id, merged_pdf_url, documents[]
# sk_test_ renders staging, with a STAGING watermarkA workflow puts several templates behind one set of data. Your system or a web form sends the policy data once, the include rule on each document decides whether it belongs, every included document fills from the same values, and Mezdoc returns one merged packet, the separate files, or both.
No. Your PAS, AMS or rater stays the system of record for policies, rating and binding. Mezdoc is the document layer beside it: it receives the data your systems send and returns finished documents.
Mezdoc has no prebuilt PAS, AMS or rater connectors. Your system sends JSON to the REST API, and a signed webhook tells it when the packet is ready. Teams without an integration yet use a hosted web form, or a short script that posts rows from an export.
A static PDF template is a PDF you already use, such as an ACORD form or a carrier form, with fields placed on it, so its layout never changes. A dynamic document is written in Mezdoc's editor, so its clauses and tables change with the data. One workflow can hold both.
Your team. You write an include rule on each document, such as state == "FL" or additional_insured == true, and Mezdoc applies it the same way on every run. Mezdoc does not decide which forms a risk legally needs.
Free plan, no card