MARITIME PORT DATA API

Build on one canonical harbour layer instead of reconciling it yourself

MaritimIQ provides a commercial `/v1` API for products that need more than a port name and coordinates. Stable identities, aliases, infrastructure, vessel-fit reasoning, services, warnings, evidence and licensing semantics arrive through one versioned contract.

Explore the portal See API access

Resolve fragmented names and external identifiers to canonical harbour UUIDs.

Add port intelligence without turning nulls into false negatives or estimates into official truth.

Consume change events and govern distribution with scopes, plans and licensing-aware responses.

WHY THIS ROLE NEEDS IT

Replace fragmented research with a governed record.

Use structured harbour intelligence in underwriting, due diligence, public planning and software products.

Port identity is harder than a name

Aliases, local spellings, UN/LOCODE, WPI and place-level concepts can refer to one harbour—or to several distinct facilities.

Schemas often erase uncertainty

A boolean cannot represent unknown, conflicting, stale, not covered and known-no without losing operational meaning.

Licensing follows the field

A response must consider whether the underlying source permits redistribution, not merely whether the application can read the value.

MaritimIQ canonical harbour search interface backed by the port data API — Searchable harbour ledger
The human interface and API resolve to the same canonical harbour concepts and truth states.
Open in portal

ROLE-SPECIFIC FEATURES

The product capabilities that matter to software & api teams.

Canonical identity graph

Use UUIDs, identifiers, aliases and current/historical locations to reconcile downstream records.

Versioned REST API and OpenAPI

Build against documented `/v1` routes and a machine-readable contract.

Commercial access control

Use live and sandbox bearer keys, scopes, plan entitlements, rate limits and durable usage metering.

Truth-state semantics

Receive confidence, provenance, UNKNOWN, conflicts and coverage states rather than flattened marketing claims.

Changes and freshness

Query governed change events and domain freshness states for downstream monitoring workflows.

USE CASES

Where the database earns its place.

Yacht-management platform

Add vessel-aware harbour dossiers and arrival briefs inside an existing operations product.

Booking or marina marketplace

Enrich discovery with canonical infrastructure and suitability while keeping real availability in the booking source.

Travel or concierge app

Connect yacht ports to airports, services and destination context without mislabelling estimated relationships.

COMMERCIAL API ACCESS

Use the same intelligence in your own systems.

Start with the OpenAPI document and sandbox keys, then request only the scopes your product needs. Health and readiness are public; commercial harbour routes require authenticated access.

Developer documentation API reference

Useful endpoints for Software & API teams

GET/v1/harbors

Search the public-eligible canonical worldwide corpus.

GET/v1/openapi

Generate clients and validate the versioned contract.

POST/v1/compatibility

Add explainable vessel-to-harbour evaluation.

GET/v1/changes

Integrate governed, filterable change events.

Bearer keys, plan-aware limits and explicit scopes apply. API output is decision support—not a navigational chart, safety approval or live berth reservation.

Explainable vessel compatibility result available through the MaritimIQ API — Vessel-to-harbour feasibility
Downstream software can render the reasoned result without inventing a berth or safety approval.
Open in portal

A PRACTICAL WORKFLOW

Evidence in. Clear next step out.

Prototype

Use sandbox credentials and OpenAPI to map the contract into your product.

Govern

Select scopes, entitlements and redistribution rules for the use case.

Operate

Meter usage, handle explicit errors and consume change events without losing semantics.

TRUST MODEL

Honest about the limits of maritime data.

Provenance visible

Decision-critical facts keep their source, observed date, confidence and conflict state.

UNKNOWN stays UNKNOWN

Missing evidence is never quietly translated into no, zero, available or safe.

Licensing-aware

Accessible source material and permitted redistribution remain separate decisions.

QUESTIONS

Frequently asked.

Is there a sandbox API?

Yes. Sandbox `miq_test_` keys are distinct from production `miq_live_` keys and support controlled integration testing.

How does the API represent missing data?

Endpoints use explicit UNKNOWN, NOT_COVERED or INSUFFICIENT_DATA states where applicable rather than treating an absent value as zero or no.

Can the API power navigation or berth booking?

It can enrich those products with harbour intelligence, but it is not an official chart service and does not create availability. Navigation and booking sources remain separate.