Skip to content

Developers

The ADAM API is a modern geospatial service implementing OGC API — Features and OGC API — Tiles. It is the same backbone that powers the Live Map, and it is open and free to consume.

If you are integrating ADAM data into a dashboard, a web map, an analytical pipeline, or any system that needs near real-time disaster information, this section is for you.

At a glance
Base URL https://api.adam.geospatial.wfp.org/api
Standards OGC API — Features, OGC API — Tiles
Auth None (public, read-only)
Formats GeoJSON (features), MVT (tiles), TileJSON, StyleJSON
Interactive docs /docs
OpenAPI spec /openapi.json

Three surfaces, one API

ADAM gives you three complementary ways to explore and consume its data. Each surface has one job; using them together is what makes the experience organic.

1. Swagger UI — the formal contract

Where: /api/docs

Auto-generated from the OpenAPI spec. It is the source of truth for every endpoint: parameters, request shapes, response schemas, error codes. It also provides a Try it out button that calls the live API from your browser.

Use it when you need to:

  • Confirm the exact parameter name or type
  • See the full response schema
  • Quickly test a call without writing code

2. Live HTML browser — the data, navigable

Where: append ?f=html to any endpoint (or just open it in a browser — HTML is often the default)

Every endpoint renders as an interactive page with breadcrumbs and links. You can walk the API like a website: landing → /collections → a collection → its items → a single feature → its map.

Use it when you need to:

  • See what is in the API right now (not just what could be)
  • Eyeball a collection before writing code
  • Share a link to a specific feature or map preview

3. This documentation — the narrative

Where: you are here.

Teaches the model, orients you through the surfaces, and provides ready-to-run recipes. We deliberately do not re-document what Swagger and the HTML browser already do; instead, every reference page links directly to them.

Use this section when you need to:

  • Understand the conceptual model (collections, items, tiles, CQL2)
  • Follow a tutorial end-to-end
  • Find a task recipe (filter features, render a map, fetch event outputs)
  • See ADAM-specific patterns that the generic OGC spec does not cover

Where to start

  • New to the API?

    A 10-minute tour of all three surfaces — Swagger, the live HTML browser, and your own code.

    Quickstart

  • Need the data model?

    Collection / item / queryable, features vs tiles, dynamic fields, CQL2 — all the concepts in one page.

    Concepts

  • Know what you want?

    Endpoint and collection reference, with deep-links to the live Swagger UI.

    Reference

  • Have a specific task?

    Task-oriented recipes: filter features, render maps, fetch event outputs, recurring date queries.

    How-to Guides

Conventions used in this section

  • Code examples are in Python with httpx unless otherwise noted
  • Map examples use MapLibre GL JS
  • CLI snippets are rendered with termynal for an animated-terminal feel
  • Every Reference page closes with a Live references admonition linking directly into Swagger and the HTML browser for the endpoints it documents