API documentation

Use Maio's public collections, places, datasets and calculated astronomy in your own tools. The API is read-only and requires no API key.

GET, HEAD, OPTIONSJSON and GeoJSONNo authentication

Quickstart

Send a GET request to the base URL. For example, this returns the first ten beach features:

GET https://api.maio.cv/api/v1/collections/beaches/items?limit=10

View example response

Conventions

Pagination: use limit (1–500) and offset; follow links.next until it is null.
Search: q searches names and source attributes. bbox uses west,south,east,north in longitude,latitude order.
Provenance: check source IDs, dates, units, geometry status and caveats. Some entries are planned or have no records.
Responses: successful requests return JSON or GeoJSON. Invalid queries return 400; unknown resources return 404. Content revisions are distinct from observation dates.

Who fishes Maio's waters?

Explore weekly AIS vessel presence in the Cabo Verde EEZ and four Maio marine protected areas. Start with the EEZ summary, then use the records endpoint for flag and area filters. These routes read from a daily cache and need no API key.

Presence hours count AIS positions, not fishing activity. Many small local boats do not carry or broadcast AIS, so they will not appear. Data can lag up to 96 hours. Powered by Global Fishing Watch.

API documentation

Quickstart

Conventions

Who fishes Maio's waters?

Discovery and sources

Vessel presence

Places and map features

Datasets and statistics

Astronomy and environment

Quickstart

Conventions

Who fishes Maio's waters?

Discovery and sources

GET/api/v1/API discovery

GET/api/v1/healthSnapshot health

GET/api/v1/sourcesSource provenance, timestamps, checksums and licensing

GET/api/v1/openapi.jsonThis OpenAPI document

GET/api/v1/catalogDiscover collections, datasets and source contracts together

GET/api/v1/sources/{sourceId}Source origin, provenance, transformation, refresh and dependent resources

Vessel presence

GET/api/v1/datasets/vessel-presenceAIS vessel presence metadata, areas and weeks

GET/api/v1/datasets/vessel-presence/recordsWeekly AIS vessel presence records

GET/api/v1/vessel-presence/summaryAIS vessel presence summary

Places and map features

GET/api/v1/collectionsList available and planned collections

GET/api/v1/collections/{collectionId}Collection metadata

GET/api/v1/collections/{collectionId}/itemsPaginated GeoJSON collection

GET/api/v1/featuresSearch features across collections

GET/api/v1/features/{featureId}Get a stable feature ID

GET/api/v1/placesDiscover stable locality entities

GET/api/v1/places/{placeId}Place identity, source geometry and related-data links

GET/api/v1/places/{placeId}/featuresExplicitly associated source features; not a containment query

GET/api/v1/places/{placeId}/infrastructureExplicitly associated public infrastructure

GET/api/v1/places/{placeId}/datasetsDatasets with explicit locality links; excludes inferred island totals

Datasets and statistics

GET/api/v1/datasetsDashboard dataset metadata

GET/api/v1/datasets/{datasetId}Full source dataset, including units, scope and caveats

GET/api/v1/datasets/{datasetId}/recordsNormalized indicators where connected; planned otherwise. Legacy payloads remain at dataset detail.

GET/api/v1/transportTransport capabilities; operational feeds currently planned

GET/api/v1/transport/routesPlanned transport routes; no connected operational feed

GET/api/v1/transport/schedulesPlanned transport schedules; no connected operational feed

GET/api/v1/transport/arrivalsPlanned transport arrivals; no connected operational feed

GET/api/v1/transport/departuresPlanned transport departures; no connected operational feed

GET/api/v1/agricultureAgriculture coverage, calculated indicators and limitations

GET/api/v1/agriculture/overviewAlias of the agriculture overview

GET/api/v1/agriculture/land-useSource classifications and unioned geodesic area by class

GET/api/v1/agriculture/areasMaio Carta Agrícola polygons as paginated GeoJSON

GET/api/v1/geo/agricultureGeographic alias of /agriculture/areas

Astronomy and environment

GET/api/v1/observationsSourced environmental records; model estimates are labeled explicitly

GET/api/v1/observations/{observationId}Observation by stable source/parameter/time ID

GET/api/v1/sensorsRegistered physical sensors; currently planned

GET/api/v1/sensors/{sensorId}Registered sensor by stable ID

GET/api/v1/observation-parametersWeather, ocean, water, energy and air parameter capabilities

GET/api/v1/night-skyYear-round calculated Sun/Moon almanac for Maio; not weather or observed visibility

GET/api/v1/night-sky/constellationsConstellation pattern horizon status and reference-point direction for a specified instant

GET/api/v1/astronomyDiscover available astronomy capabilities and explicitly planned feeds

GET/api/v1/astronomy/skySun, Moon and constellation snapshot at a local date and time

GET/api/v1/astronomy/moonMoon phase and geometric position at the requested time; rise/set for that local date

GET/api/v1/astronomy/constellationsOne constellation sample per day for a month or a single date; not whole-month continuous visibility

GET/api/v1/astronomy/meteor-showersPlanned: no reviewed meteor catalogue or year-specific predictions connected

GET/api/v1/astronomy/dark-sky-spotsPlanned: no verified stargazing-site inventory connected

GET/api/v1/astronomy/stargazing-scorePlanned: null score until methodology and suitable live inputs are connected

GET/api/v1/astronomy/sky-mapWorldwide star-pattern geometry for the stargazing app; all 88 constellations

GET/api/v1/astronomy/almanacCanonical full-year Sun/Moon almanac; existing /night-sky remains compatible