Certificate of Insurance API for ACORD 25 Data Extraction

Upload a certificate of insurance below and see gaps, limits and expiration dates in seconds. No account needed.

PDF, JPG, PNG, BMP, HEIC, TIFF

Upload your certificates of insurance

No certificate on hand? Loading the sample certificate...

Free demo, no account needed. See plans and prices

The COISoftware certificate of insurance API takes a COI as a PDF, scan or phone photo and returns the named insured, certificate holder, insurers, policy numbers, effective and expiration dates and limits as structured JSON. Property management, procurement and compliance products use it to stop retyping certificates. Try the extraction on a real certificate below, then wire the same result into your own system.

Three calls from upload to JSON
Bearer token authentication
Reads scans and phone photos
Free 10-document demo

Build Your Own COI Parser or Call the API

What a product team takes on when it reads certificates itself, compared with calling an endpoint that already does.

Reading an ACORD 25

COISoftware API
AI extraction of the form fields, including scans and photos
Build in house
Template rules per insurer layout, brittle when a form is shifted or scanned at an angle

Coverage tables

COISoftware API
Table fields returned with rows and cells, one row per coverage line
Build in house
Custom code to split general liability, auto, umbrella and workers comp rows

Endorsement pages

COISoftware API
Endorsement pages attached to the certificate count as part of the same document
Build in house
Usually skipped, so the additional insured box is trusted on its own

Fixing bad reads

COISoftware API
Documents that stop are returned with a status and a plain message
Build in house
Your support team inherits every misread date

Time to first result

COISoftware API
An API token and three HTTP calls
Build in house
Weeks to months of parser work and test certificates

Cost

COISoftware API
Included in the Pro and Enterprise plans, listed on the pricing page
Build in house
Engineering time plus ongoing maintenance as forms change

API access is part of the Pro and Enterprise plans. Starter and Plus accounts can export every result to Excel or CSV from the dashboard.

Why Teams Stop Hand Keying Certificates

A product that touches vendor insurance eventually needs the data off the certificate, and keying it in does not scale.

Certificates are not structured data

The ACORD 25 is a form designed to be read by people. Every agency exports it a little differently, and many arrive as scans.

One misread date is a coverage gap

An expiration date typed as 2026 instead of 2027 hides a lapse for a year or shows a live policy as expired.

Coverage lives in tables

General liability, auto, umbrella and workers compensation each have their own limits and dates, so a flat field list is not enough.

Volume arrives in bursts

Renewal season sends hundreds of certificates in a week, which is exactly when a manual queue falls behind.

Maintenance never ends

A parser built for ten layouts breaks on the eleventh, and somebody on your team owns that forever.

Teams usually reach for an API at one of two moments. A property management or procurement product already stores vendors and now needs the insurance data attached to each one. Or an operations team has a back office system and wants certificates to land in it without a person in the middle. In both cases the extraction is the hard part, and the rest is ordinary integration work. See the build versus buy breakdown for the numbers behind that choice.

What the Certificate of Insurance API Gives You

Upload, extract and read the result. The same engine that powers the dashboard, available to your code.

Upload endpoint

POST a certificate as multipart form data and get back a file ID to extract from.

Extraction endpoint

Start extraction for the uploaded file and get an extraction hash to poll with.

Structured JSON result

Fields come back with labels and values, and table fields such as the coverage lines come back as rows and cells.

Scoped API tokens

Create tokens in your dashboard and limit each one to the abilities it needs, such as upload only or read only.

Clear status and messages

A document is pending, processing, completed or stopped, and a stopped one tells you why in a sentence you can show a user.

Excel and CSV on every plan

Not every team needs an integration. Every plan exports the same data to XLSX and CSV from the dashboard.

The endpoints, parameters and sample code in PHP, JavaScript and cURL are on the API documentation page. If you want the full vendor workflow without writing code, see COI management software, and for the requirements check that sits after extraction, see certificate of insurance verification.

Why Choose COISoftware?

  • Three HTTP calls from file to JSON
  • Works on PDFs, scans and phone photos
  • Coverage lines returned as table rows
  • Token abilities you control per integration
  • Same engine as the dashboard
  • Built for US ACORD certificates

How to Call the Certificate of Insurance API

From a Pro plan token to parsed coverage data.

1

Create an API token

On a Pro or Enterprise plan, open the API section of your dashboard and create a token with the abilities you want, then send it as a Bearer token.

Tip: Use one token per integration so you can revoke one without touching the rest.

2

Upload the certificate and start extraction

POST the file to the upload endpoint, then POST the file ID to the extract endpoint. You get an extraction hash back.

3

Poll for the result

GET the extraction by hash until the status is completed, then read the fields and coverage rows from the JSON.

Who Uses a COI Extraction API

Teams that already have vendors in a system and need the insurance data to follow them there.

Vendors of property management and facilities software add certificate intake to their own product instead of building a parser. Procurement and vendor onboarding platforms attach coverage data to each supplier record. Construction technology teams push subcontractor certificates into project tools, see COI tracking for Procore and COI tracking for QuickBooks for the workflows built around those systems. Internal operations teams use it to feed a data warehouse or an approval flow. For the OCR step in isolation, see certificate of insurance OCR.

Why Developers Pick COISoftware

3
Calls from upload to result
JSON
Fields and coverage rows
Pro
API on Pro and Enterprise plans

What you can count on

  • Token authentication with scoped abilities
  • Encrypted storage of every certificate
  • Your certificate data is never sold or shared
  • Built for US ACORD certificates

Certificate of Insurance API FAQ

It accepts a certificate file and returns its contents as structured data. With COISoftware you upload a COI, start extraction, and read the named insured, certificate holder, insurers, policy numbers, dates and limits as JSON instead of retyping them.

The Pro and Enterprise plans include the API. Starter and Plus accounts cannot call the endpoints, but every plan can export extracted data to Excel and CSV. Current plan details are on the pricing page.

Yes. Extraction works on PDFs, scans and phone photos of an ACORD 25. A file that is not a certificate, or is over the page limit of your plan, stops with a status and a message you can pass on to the user.

Create a personal API token in your dashboard and send it in the Authorization header as a Bearer token. Each token can be limited to specific abilities, such as uploading documents or viewing extractions.

Yes. Coverage lines come back as a table field with one row per coverage, including coverage type, insurer, policy number, effective and expiration dates and limits. Header fields such as named insured and certificate holder come back as separate fields.

Yes. Upload a certificate to the demo on this page with no account, and a free signup adds a demo of 10 documents. You see the same extraction the API returns before you pick a plan.