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

1Fort application (v2): coverages API

**Access:** requires a JWT access token.

1Fort application (v2): coverages API is one of 89 APIs that 1Fort publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include application (v2): coverages. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, authentication docs, and rate-limit docs.

This API exposes 17 operations across 13 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.1fort.com/apis/.

17 operations 13 paths 12 schemas 8 GET2 PATCH5 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.1fort.com/apis/
Authentication
API Key, API Key
License
Privately owned
Terms of Service
Resource Areas
1

Authentication & Security 2

1Fort application (v2): coverages API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (Bearer). An API key is passed in the header as Authorization (ApiKey). By default, every request must be authenticated.

  • Bearer — JWT access token. Send as Bearer or JWT .
  • ApiKey — API key. Send as Api-Key .

Paths & Operations 17

Across 13 paths, the API surfaces 17 operations — 8 GET, 2 PATCH, 5 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

application (v2): coverages 17

Access: requires a JWT access token.

GET
/v2/broker/{business_pk}/coverages
List Coverages
v2_broker_coverages_list 5 params → 200403500
GET
/v2/broker/{business_pk}/coverages/{id}
Retrieve Coverage
v2_broker_coverages_read 2 params → 200403404500
PUT
/v2/broker/{business_pk}/coverages/{id}
Update Coverage
v2_broker_coverages_update 2 params body → 200400403404500
PATCH
/v2/broker/{business_pk}/coverages/{id}
Update Coverage
v2_broker_coverages_partial_update 2 params body → 200400403404500
GET
/v2/broker/{business_pk}/coverages/{id}/accord-forms/{accord_form_pk}/acroform-pdf
Stream the blank Acroform PDF of an ACORD form linked to this coverage.
v2_broker_coverages_accord-forms_accord_form_acroform_pdf 3 params → 200403404500
GET
/v2/broker/{business_pk}/coverages/{id}/accord-forms/{accord_form_pk}/mapping-file
Accord form mapping file
v2_broker_coverages_accord-forms_accord_form_mapping_file 3 params → 200403404500
POST
/v2/broker/{business_pk}/coverages/{id}/answer-with-ai
Kick off AI web research to guess answers for the coverage application's rawquestionvalues.
v2_broker_coverages_answer_with_ai 2 params body → 201400403404500
GET
/v2/broker/{business_pk}/coverages/{id}/answer-with-ai/{task_id}
Answer with AI result
v2_broker_coverages_answer_with_ai_result 3 params → 200403404500
POST
/v2/broker/{business_pk}/coverages/{id}/approve
Approve
v2_broker_coverages_approve 2 params body → 201400403404500
POST
/v2/broker/{business_pk}/coverages/{id}/submit
Submit a coverage application using the submission service.
v2_broker_coverages_submit 2 params body → 201400403404500
GET
/v2/broker/{business_pk}/coverages/{id}/supplemental-application-pdf
Generate and stream the supplemental application PDF for preview.
v2_broker_coverages_supplemental_application_pdf 2 params → 200403404500
GET
/v2/coverages
List Coverages
v2_coverages_list 4 params → 200403500
GET
/v2/coverages/{id}
Retrieve Coverage
v2_coverages_read 1 param → 200403404500
PUT
/v2/coverages/{id}
Update Coverage
v2_coverages_update 1 param body → 200400403404500
PATCH
/v2/coverages/{id}
Update Coverage
v2_coverages_partial_update 1 param body → 200400403404500
POST
/v2/coverages/{id}/collect-signatures
Collect signatures
v2_coverages_collect_signatures 1 param body → 201400403404500
POST
/v2/coverages/{id}/submit
Submit a coverage application as a business user using the submission service.
v2_coverages_submit 1 param body → 201400403404500

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are BrokerCoverageApplicationWithCompositeResponse (33 properties), CoverageApplicationWithCompositeResponse (32 properties), CoverageApplicationUpdate (18 properties), ProductLine (9 properties). Each schema is shown below with its type and property counts.

ValidationError
object
1 property
CoverageApplicationWithCompositeResponse
object
32 properties 2 required
SubProductLine
object
5 properties
CoverageApplicationUpdate
object
18 properties
ParameterValueUpdate
object
6 properties 1 required
CanonicalProductLineRef
object
3 properties 1 required
GenericError
object
1 property 1 required
CoverageAccordForm
object
7 properties 1 required
APIException
object
1 property 1 required
BrokerCoverageApplicationWithCompositeResponse
object
33 properties 2 required
ProductLine
object
9 properties 1 required
CarrierList
object
5 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

1fort-application-v2-coverages-api-openapi.yml Raw ↑

Other APIs 1Fort publishes across the network.

1Fort agent_runtime (v2) API
1Fort Analytics API
1Fort application: applications API
1Fort application: clients API
1Fort application (v2): applications API
1Fort Ascend API
1Fort ascend (v2) API
1Fort Auth API
1Fort Authentication API
1Fort billing (v2) API
1Fort broker: ai-customization-types API
1Fort broker: ai-customizations API
Where this information came from

This is an independent, third-party profile of 1Fort application (v2): coverages 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.