How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ACORD Policy API

Policy administration and management

ACORD Policy API is one of 6 APIs that ACORD publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 5 JSON Schema definitions.

Tagged areas include Policy. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and 5 JSON Schemas.

This API exposes 4 operations across 2 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.insurer-internal.example.com/ngds.

4 operations 2 paths 12 schemas 2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
https://api.insurer-internal.example.com/ngds
Authentication
OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 2

ACORD Policy API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the clientCredentials flow, exposing 4 scopes. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Policy 4

Policy administration and management

GET
/policies
ACORD List Policies
listPolicies 6 params → 200401403
POST
/policies
ACORD Create a New Policy
createPolicy body → 201400401
GET
/policies/{policyId}
ACORD Get Policy by ID
getPolicy 1 param → 200404
PATCH
/policies/{policyId}
ACORD Update Policy
updatePolicy 1 param body → 200404

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are Policy (12 properties), Party (8 properties), PolicyRequest (7 properties), PartyRequest (7 properties). Each schema is shown below with its type and property counts.

PolicyRequest
object
7 properties 4 required
PolicyUpdate
object
4 properties
Party
object
8 properties
PolicyList
object
2 properties
Coverage
object
6 properties
Contact
object
2 properties
CoverageRequest
object
5 properties 2 required
PartyRequest
object
7 properties 1 required
Policy
object
ACORD NGDS Policy object representing an insurance contract
12 properties
Pagination
object
4 properties
Error
object
3 properties
Address
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

acord-policy-api-openapi.yml Raw ↑

Other APIs ACORD publishes across the network.

ACORD XML Standards API
ACORD Reinsurance & Large Commercial Data Standards API
ACORD Claims API
ACORD Party API
ACORD Underwriting API
Where this information came from

This is an independent, third-party profile of ACORD Policy API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.