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

Prewave Exposure API

Get exposure analysis graph and targets

Prewave Exposure API is one of 25 APIs that Prewave publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

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

4 operations 4 paths 73 schemas 2 GET2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.prewave.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Prewave Exposure API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Auth-Token (Token_authentication). By default, every request must be authenticated.

  • Token_authentication — Generate an API token at https://www.prewave.com/management/api and paste it in here.

Paths & Operations 4

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

Exposure 4

Get exposure analysis graph and targets

PUT
/public/v1/alpha/exposure/target/{targetId}/graph
Get exposure graph by target id
getExposureGraphByTargetId 1 param body → 200403500429
PUT
/public/v1/alpha/exposure/target/{systemId}/{targetId}/graph
Get exposure graph by foreign system target id
getExposureGraphByForeignSystemTargetId 2 params body → 200403500429
GET
/public/v1/alpha/exposure/{id}
Get exposure analysis info by exposure analysis id
getExposureAnalysisById 1 param → 200403500429
GET
/public/v1/alpha/exposure/{id}/graph
Get exposure graph by exposure analysis id
getExposureGraphById 2 params → 200403500429

Schemas 73

The contract defines 73 schemas that model the data the API accepts and returns. The most detailed are TargetDTO (64 properties), CollectionDTO (29 properties), UserDTO (27 properties), EdgeImpactData (26 properties). Each schema is shown below with its type and property counts.

Data
object
1 property 1 required
Connection
object
11 properties 7 required
RiskAnalysisType
object
12 properties 7 required
ExposureFilter
object
5 properties 3 required
CollectionDTO
object
29 properties 16 required
CommodityFilter
object
3 properties 3 required
TierSettingsDTO
object
18 properties 14 required
RiskAnalysisLock
object
4 properties 2 required
EdgeImpactData
object
26 properties 9 required
UserAttributes
object
1 property 1 required
BaseExposurePayload
object
21 properties 14 required
DisruptionStatus
object
5 properties 5 required
CollectionRef
object
Paths of the target in the collection hierarchy
2 properties 2 required
DeliverySettingTypeDTO
object
6 properties 6 required
Geo
object
Geo information for this alert. Only available if includeGeo is set to true.
3 properties 2 required
PredictionData
object
1 required
ExplorerLinkSet
object
3 properties 3 required
TargetRequestTypeStatusDto
object
4 properties
PlanTypeDTO
object
4 properties
TargetRef
object
5 properties 3 required
TeamDTO
object
4 properties 3 required
InfotagGroup
object
5 properties 4 required
CommodityFilterId
object
3 properties 3 required
PermissionDTO
object
4 properties 2 required
ExposureGraph
object
5 properties 5 required
PerspectiveTypeDTO
object
4 properties 4 required
CustomerData
object
RoleDTO
object
6 properties 3 required
ExposureCommodity
object
2 properties 2 required
SupplierOnboardingData
object
2 properties 2 required
TargetTypeDTO
object
6 properties 5 required
ExplorerTier
object
2 properties 2 required
PlanLimitDTO
object
2 properties 2 required
CustomsData
object
2 required
RiskAnalysis
object
25 properties 20 required
UserSettings
object
2 properties 2 required
AccessDeniedErrorDTO
object
5 properties 3 required
GeoProperties
object
4 properties
EdgeDetails
object
3 properties 3 required
ExplorerLink
object
5 properties 4 required
InfotagDTO
object
10 properties 3 required
ExplorerTargetRef
object
2 properties 2 required
ExposureTarget
object
2 properties 2 required
ExposureTargetDetails
object
7 properties 6 required
ExposureRiskTarget
object
8 properties 7 required
InfotagTypeDTO
object
6 properties 4 required
EdgeNumber
object
3 properties 1 required
Shipment
object
3 properties 1 required
BaseTarget
object
6 properties 5 required
UserSystemAttributes
object
4 properties 2 required
ExposureReason
object
2 properties 2 required
EdgeDTO
object
18 properties 11 required
ApiRateLimitTimeRequestLimit
object
Rate limit configuration for a specific time window
2 properties
ComplexDisruptionStatusUpdate
object
Disruption status update of the target
2 properties 2 required
TargetCTypeDTO
object
11 properties 10 required
ExposureAnalysis
object
25 properties 18 required
DisruptionStatusUpdate
object
10 properties 4 required
ExposureTargetStat
object
2 properties 2 required
Geometry
object
GeoJSON-compatible geometry object. Fields follow the GeoJSON spec (https://geojson.org): a type string (e.g. Point, Polygon) and a coordinates array.
MediaData
object
1 required
HSCode
object
6 properties 3 required
ExplorerTarget
object
10 properties 5 required
ApiRateLimitResponse
object
Response returned when API rate limit is exceeded (HTTP 429)
7 properties
ErrorDTO
object
Error response
3 properties 2 required
UserDTO
object
27 properties 3 required
TargetForeignSystemDTO
object
3 properties 2 required
RoleTypeDTO
object
3 properties 3 required
CustomerDTO
object
7 properties 3 required
TargetRequestInfoDto
object
4 properties 1 required
TargetDTO
object
64 properties 25 required
PerspectiveDTO
object
20 properties 16 required
PlanDTO
object
7 properties 1 required
ExplorerGraph
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

prewave-exposure-api-openapi.yml Raw ↑

Other APIs Prewave publishes across the network.

Prewave Actions API
Prewave Alerts API
Prewave Collections - Management API
Prewave Collections - Network API
Prewave Collections - Targets API
Prewave Collections - Tier-N API
Prewave Disruptions API
Prewave EUDR - Customers - DDS API
Prewave EUDR - Customers - Origin Requests API
Prewave EUDR - Customers - Products API
Prewave EUDR - Customers - Suppliers API
Prewave EUDR - Shared API
Where this information came from

This is an independent, third-party profile of Prewave Exposure 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.