Connect UWOne Verify to your systems
Keep your project management tool, ERP or vendor database in step with certificate compliance. A REST API manages third parties and certificates; webhooks tell your system the moment a result is in.
Sync your subcontractors
Create and update third parties with your own IDs, and assign the insurance they must carry.
Send in certificates
Submit certificate PDFs from your system, or let third parties email them as usual.
Get results pushed
Signed webhooks when a certificate is approved, rejected or needs review, with the PDF one call away.
A typical project management integration: create each subcontractor with your system’s ID as externalId, assign a requirement set, then listen for certificate.processed and update the subcontractor’s record (and attach the certificate) in your tool.
Authentication
An organization admin creates API keys in UWOne Verify under Settings → API & webhooks. Send the key as a bearer token on every request, over HTTPS:
curl https://verify.underwriteone.com/api/v1/third-parties \
-H "Authorization: Bearer $UWONE_API_KEY"Each key carries one or more permissions:
configure_spec— create and update third parties and requirement sets, and assign requirement sets.analyze_docs— submit certificates for checking. Certificates submitted by API count toward your plan exactly like emailed ones.read_status— read third parties, status, results and certificate PDFs.
Base URL: https://verify.underwriteone.com/api/v1. Requests and responses are JSON unless noted.
Third parties
The subcontractors, vendors, tenants and others you need certificates from. Give each one your own externalId (unique in your organization) to find it again from your system.
/third-partiesconfigure_specCreate a third party. relationship is one of subcontractor, vendor, supplier, tenant, consultant, other.
curl -X POST https://verify.underwriteone.com/api/v1/third-parties \
-H "Authorization: Bearer $UWONE_API_KEY" -H "Content-Type: application/json" \
-d '{
"name": "Acme Roofing LLC",
"contactEmails": ["certs@acmeroofing.com"],
"relationship": "subcontractor",
"externalId": "vendor-48213"
}'
# 201 Created
{ "thirdPartyId": "k57...", "thirdParty": { "id": "k57...", "externalId": "vendor-48213", "name": "Acme Roofing LLC", ... } }/third-partiesread_statusList third parties, oldest first, 50 per page (limit up to 100). Pass nextCursor back as cursor for the next page; it’s null on the last. Add ?externalId=vendor-48213 to look one up by your ID.
{
"data": [
{
"id": "k57...",
"externalId": "vendor-48213",
"name": "Acme Roofing LLC",
"aka": [],
"contactEmails": ["certs@acmeroofing.com"],
"relationship": "subcontractor",
"agencyId": null,
"status": "active",
"createdAt": "2026-11-13T15:04:05.000Z"
}
],
"nextCursor": null
}/third-parties/{id}read_statusOne third party, in the same shape.
/third-parties/{id}configure_specChange any of name, aka, contactEmails, relationship, agencyId, externalId, status (active | inactive). Only the fields you send change; null clears one. Returns the updated third party.
{ "contactEmails": ["insurance@acmeroofing.com"], "externalId": "vendor-48213" }/third-parties/{id}/assignmentsconfigure_specAssign a requirement set, which starts tracking this third party’s certificates against it from startDate.
{ "requirementSetId": "j97...", "startDate": "2026-11-13" }
# 201 Created
{ "complianceTermId": "m12..." }/third-parties/{id}/statusread_statusWhere this third party stands on each requirement set assigned to it.
{
"thirdPartyId": "k57...",
"externalId": "vendor-48213",
"terms": [
{
"requirementSetName": "General Contractors",
"status": "approved",
"certificateSubmissionId": "n44...",
"lastSubmissionAt": 1794580000000,
"endDate": "2027-11-13",
"daysUntilEnd": 365,
...
}
]
}status is approved, rejected, escalated (waiting for a person on your team), processing, or pending (no certificate yet).
Requirement sets
The insurance a third party must carry: coverage types, limits and endorsements. Most customers set these up in the app; the API can read and manage them too.
/requirement-setsconfigure_specAll your requirement sets: { "requirementSets": [...] }.
/requirement-setsconfigure_specCreate one. analysisTier is A (strict), B (standard) or C (AI-assisted). Limits are in dollars.
{
"name": "General Contractors",
"analysisTier": "B",
"toleranceConfig": { "allowTierCAutoApprove": false },
"complianceTermConfig": { "lengthDays": 365 },
"coverageRequirements": [
{
"coverageType": "general_liability",
"requiredLimits": { "each_occurrence": 1000000, "general_aggregate": 2000000 },
"requiredEndorsements": ["additional_insured", "waiver_of_subrogation"]
}
],
"certificateHolderNames": ["Your Company LLC"]
}
# 201 Created
{ "requirementSetId": "j97..." }/requirement-sets/{id}configure_specChange name, toleranceConfig, coverageRequirements or certificateHolderNames.
Certificates
Third parties usually email certificates to their own address in UWOne Verify. You can also submit them from your system. Either way, each one is read, checked against the requirement set, and approved, rejected or escalated for review, usually within a minute or two.
/certificate-submissions?thirdPartyId={id}analyze_docsSend the PDF itself as the request body. Add &requirementSetId= when the third party has more than one requirement set assigned.
curl -X POST "https://verify.underwriteone.com/api/v1/certificate-submissions?thirdPartyId=k57..." \
-H "Authorization: Bearer $UWONE_API_KEY" \
-H "Content-Type: application/pdf" \
--data-binary @certificate.pdf
# 202 Accepted
{ "certificateSubmissionId": "n44..." }/certificate-submissions/{id}read_statusThe result, once checking finishes (result is null until then). Each check explains itself in plain language.
{
"certificateSubmissionId": "n44...",
"kind": "initial",
"result": {
"status": "rejected",
"isOverridden": false,
"checks": [
{
"checkId": "limit_each_occurrence",
"status": "fail",
"explanation": "General Liability each occurrence is $500,000; $1,000,000 is required."
},
...
]
}
}/certificate-submissions/{id}/documentread_statusThe certificate PDF (application/pdf), e.g. to attach to the vendor’s record in your system.
Webhooks
Add an HTTPS endpoint under Settings → API & webhooks and choose its events. We POST each event as JSON:
certificate.receivedA certificate arrived, by email or the API, and is being checked.certificate.processedChecking finished: approved, rejected, or escalated for a person to review.certificate.reviewedA person on your team approved or rejected a certificate.{
"id": "evt_3f9c1e7a5b2d4c6e8f0a1b2c",
"type": "certificate.processed",
"createdAt": "2026-11-13T15:04:05.000Z",
"data": {
"certificateSubmissionId": "n44...",
"kind": "initial",
"thirdParty": { "id": "k57...", "externalId": "vendor-48213", "name": "Acme Roofing LLC" },
"complianceTermId": "m12...",
"requirementSetId": "j97...",
"result": {
"status": "rejected",
"decidedByPerson": false,
"issues": [
{
"checkId": "limit_each_occurrence",
"status": "fail",
"explanation": "General Liability each occurrence is $500,000; $1,000,000 is required."
}
]
}
}
}Verifying the signature
Requests are signed with your endpoint’s secret (shown once when you add it) using the Standard Webhooks scheme, so any Standard Webhooks library verifies them. Each request has webhook-id, webhook-timestamp and webhook-signature headers.
// Node.js, with the "standardwebhooks" package
import { Webhook } from "standardwebhooks";
const wh = new Webhook(process.env.UWONE_WEBHOOK_SECRET); // "whsec_..."
app.post("/webhooks/uwone", express.raw({ type: "application/json" }), (req, res) => {
const event = wh.verify(req.body, req.headers); // throws if the signature is wrong
if (event.type === "certificate.processed") {
// update the subcontractor in your system, using event.data.thirdParty.externalId
}
res.sendStatus(200);
});Without a library: the signature is v1, followed by the base64 HMAC-SHA256 of {webhook-id}.{webhook-timestamp}.{raw body}, keyed with the base64-decoded part of your secret after whsec_.
Delivery
- Reply with any 2xx status within 10 seconds. Do slow work after you reply.
- Anything else is retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours, then marked failed.
- The same event can arrive more than once; use
webhook-idto ignore repeats. - Send test in Settings sends a
webhook.testevent, and the endpoint’s recent deliveries show what happened to each.
Errors
Errors return a JSON body with a readable message: { "error": "..." }.
400— the request is invalid; the message says why.401— the API key is missing or wrong.403— the key lacks the permission this endpoint needs.404— no such record in your organization.
Questions, or connecting a specific tool? Email support@mail.underwriteone.com.