Voyage Risk API

Real-time, AI-verified risk alerts — delivered via REST API and webhooks.

Clean, documented JSON designed for automation into your own product, SIEM, ITSM, or data-warehouse pipelines.

Request API access Talk to sales

What the API gives you

The Voyage Risk API is a REST and webhook interface to the Voyage Risk alerting pipeline. It delivers verified, geolocated risk alerts as clean JSON, designed for long-lived automation.

REST API

Query alerts by country, severity, category, or time window. Clean, versioned JSON.

Webhooks

Alerts pushed to your endpoint the moment they publish, with filters by country, severity, or category.

Stable schemas

Documented, versioned JSON designed for automation and long-lived integrations.

Provenance on every record

Severity, category, confidence, geolocation, source references, and timestamps included on every alert.

What is in a Voyage Risk alert?

Every published alert is a structured JSON record. At a minimum it includes:

Identifier and publish timestamp
Severity, category, and confidence score
Headline and summary
Location resolved to country, state or province, city, or GPS coordinates where available
Source references
Links to the underlying record and, where applicable, its portal representation

Field-level schema documentation, exact taxonomies, and endpoint paths are shared with approved integration partners during onboarding.

Severe weather disruption

AE · Dubai · 25.2048, 55.2708

Heavy rainfall causing flooding and transport disruption.

Category: weather Alert ID: 67890 Incident ID: 12345

View JSON payload

{
  "alertId": 67890,
  "incidentId": 12345,
  "incidentLocationId": 54321,
  "feedName": "NWS",
  "externalId": "nws-abc123",
  "sourceUrl": "https://example.com",
  "headline": "Severe weather disruption",
  "description": "Heavy rainfall causing flooding and transport disruption.",
  "category": "weather",
  "severity": 3,
  "country": "AE",
  "stateOrProvince": null,
  "city": "Dubai",
  "locationLevel": "city",
  "affectedCountries": ["United Arab Emirates"],
  "affectedCountryCodes": ["AE"],
  "latitude": 25.2048,
  "longitude": 55.2708,
  "occurredUtc": "2026-04-21T10:32:00Z",
  "ingestedUtc": "2026-04-21T10:35:00Z"
}

Illustrative example. Not live data.

Working with the API

Concrete examples for integration planning. Exact base URL, authentication scheme, endpoint paths, and rate-limit policy are confirmed with approved partners during onboarding.

Base URL Example

Shown for illustration. The production base URL is confirmed during onboarding.

https://api.voyagerisk.com

Authentication

API credentials are issued during onboarding and used to authenticate requests. Specific scheme and header details are shared with approved integration partners.

Example endpoint Example

Illustrative. Exact paths are confirmed at onboarding.

GET /api/alerts

Example request Example

Filter high-severity alerts for a country.

curl -X GET "https://api.voyagerisk.com/api/alerts?country=AE&minSeverity=3" \
  -H "Authorization: Bearer <your-api-token>"

Example response

Illustrative alert payload. GET /api/alerts returns an array of alert records; a single record is shown here for clarity.

[
  {
    "alertId": 67890,
    "incidentId": 12345,
    "incidentLocationId": 54321,
    "feedName": "NWS",
    "externalId": "nws-abc123",
    "sourceUrl": "https://example.com",
    "headline": "Severe weather disruption",
    "description": "Heavy rainfall causing flooding and transport disruption.",
    "category": "weather",
    "severity": 3,
    "country": "AE",
    "stateOrProvince": null,
    "city": "Dubai",
    "locationLevel": "city",
    "affectedCountries": ["United Arab Emirates"],
    "affectedCountryCodes": ["AE"],
    "latitude": 25.2048,
    "longitude": 55.2708,
    "occurredUtc": "2026-04-21T10:32:00Z",
    "ingestedUtc": "2026-04-21T10:35:00Z"
  }
]

Access model

Voyage Risk API access is granted through an onboarding conversation, not through self-serve signup. Approved partners receive credentials, endpoint documentation, schema references, webhook configuration, sandbox access, and production rate limits.

Request API access Talk to sales

Capabilities

What you can do through REST and webhooks.

Capability

Delivery

List alerts with filters (country, severity, category, time window)

REST API

Fetch a single alert by identifier

REST API

Receive alerts on publish

Webhooks

Receive updates to previously published alerts

Webhooks

Manage webhook subscriptions and filters

REST API

Test against sandbox alerts

Sandbox environment

Exact endpoint paths, authentication, rate-limit policy, and sandbox access are shared with approved integration partners during onboarding.

How access works

Voyage Risk API access is granted through an onboarding conversation. Talk to sales to confirm your use case, preferred delivery mode (REST, webhooks, or both), and integration requirements.

Approved partners receive authentication credentials, endpoint documentation, field-level schemas, webhook configuration details, sandbox access, and production rate limits.

Request API access Talk to sales

API concepts

Concepts that shape how Voyage Risk publishes and delivers alerts.

How are alerts verified?

Voyage Risk uses AI to corroborate incoming signals across multiple sources, deduplicate near-duplicates, and track provenance on every alert. Provenance is included on every published record.

How are alerts geolocated?

Each alert is resolved to a country, and where possible to state or province, city, or GPS coordinates. Where the source input is ambiguous, that uncertainty is reflected in the confidence score.

What do severity, category, and confidence mean?

Severity reflects the potential operational impact of the event. Category describes the type of event — for example, civil unrest, severe weather, or transport disruption. Confidence reflects how certain the pipeline is of the classification and geolocation. Exact taxonomies are shared with integration partners.

How is the Voyage Risk API authenticated?

Authentication credentials are issued per environment to approved integration partners during onboarding. Detailed authentication documentation is shared at that point.

Is there a sandbox environment?

A sandbox environment is available to approved partners during integration. Contact sales to discuss access.

What are the rate limits?

Rate limits are set per integration based on use case and expected volume. They are agreed during onboarding.

Can alerts be filtered?

Yes. Alerts can be filtered by country, severity, category, and time window on the REST API, and by the same criteria on webhook subscriptions.

What format are alerts delivered in?

Alerts are delivered as JSON. Field names and structures are stable, documented, and versioned.

What if a webhook delivery fails?

Webhook delivery configuration, including retry behaviour and payload verification, is documented for integration partners during onboarding.

Which SIEM, ITSM, or data-warehouse systems does the API work with?

Voyage Risk delivers standard JSON over REST and webhooks. It does not bundle specific vendor connectors. Alerts are designed to map cleanly into common SIEM, ITSM, and data-warehouse platforms via your existing ingestion tooling.

Ready to integrate Voyage Risk?

Request API access or talk to sales about your use case.

Request API access Talk to sales