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

Precisely APIs Fire API

The Fire API from Precisely APIs — 4 operation(s) for fire.

Precisely APIs Fire API is one of 81 APIs that Precisely APIs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Fire. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 8 operations across 4 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 18.1.0.

Requests are made against a single base URL, https://api.precisely.com.

8 operations 4 paths 23 schemas 4 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
18.1.0
Server
https://api.precisely.com
Authentication
OAuth 2.0
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Precisely APIs Fire API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oAuth2Password) using the implicit flow, exposing 1 scope. By default, every request must be authenticated.

Paths & Operations 8

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

Fire 8
GET
/risks/v1/fire/bylocation
Get Fire Risk By Location
getFireRiskByLocation 3 params → 200400500
POST
/risks/v1/fire/bylocation
Post Fire Risk By Location
getFireRiskByLocationBatch body → 200400500
GET
/risks/v1/fire/byaddress
Get Fire Risk By Address
getFireRiskByAddress 2 params → 200400500
POST
/risks/v1/fire/byaddress
Post Fire Risk By Address
getFireRiskByAddressBatch body → 200400500
GET
/risks/v2/fire/bylocation
Get Fire Risk By Location
getFireRiskV2ByLocation 3 params → 200400500
POST
/risks/v2/fire/bylocation
Post Fire Risk By Location
getFireRiskV2ByLocationBatch body → 200400500
GET
/risks/v2/fire/byaddress
Get Fire Risk By Address
getFireRiskV2ByAddress 2 params → 200400500
POST
/risks/v2/fire/byaddress
Post Fire Risk By Address
getFireRiskV2ByAddressBatch body → 200400500

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are RiskAddress (30 properties), Risk (20 properties), FireRiskV2Response (19 properties), FireRiskResponse (4 properties). Each schema is shown below with its type and property counts.

CommunityGroup
object
4 properties
RiskGeometry
object
2 properties 1 required
FrequencyGroup
object
4 properties
Risk
object
20 properties
GeometryProperties
object
1 property
CommonGeometry
object
3 properties
FireShed
object
3 properties
ErrorCode
object
2 properties
FireRiskByLocationRequest
object
2 properties 1 required
State
object
2 properties
FireRiskByAddressRequest
object
2 properties 1 required
DamageGroup
object
2 properties
RiskLocations
object
3 properties 1 required
SeverityGroup
object
4 properties
RiskAddress
object
30 properties
ErrorInfo_1
object
1 property
MitigationGroup
object
4 properties
FireRiskResponse
object
4 properties
RisksGeometryCRC
object
2 properties
FireRiskV2ResponseList
object
1 property
RiskPreferences
object
3 properties
FireRiskResponseList
object
1 property
FireRiskV2Response
object
19 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

precisely-apis-fire-api-openapi.yml Raw ↑

Other APIs Precisely APIs publishes across the network.

Precisely APIs Address API
Precisely APIs Address Verification Service API
Precisely APIs Addresses API
Precisely APIs Addresses Service. API
Precisely APIs Advanced API
Precisely APIs Ahj API
Precisely APIs Attributes API
Precisely APIs Autocomplete API
Precisely APIs Basic API
Precisely APIs Bundles API
Precisely APIs Byaddress API
Precisely APIs Byarea API
Where this information came from

This is an independent, third-party profile of Precisely APIs Fire 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.