Momberger Data API

Authentication

Endpoints

# Momberger Airport Information — REST API

Base URL: https://momberger.app
Auth: every request must include `Authorization: Bearer <token>`
  - `<token>` is either a Supabase JWT (in-app sessions) or a long-lived API key
    that starts with `mbg_live_`. Generate keys at /settings → API Keys.
Content-Type: all POST bodies are JSON.
Errors: non-2xx responses return `{ "error": "<message>" }`.
Rate limits (per API key, UTC day): trial 200 / core 1k / professional 1k / enterprise 10k.
  Exceeded → 429 with `Retry-After` header.

Modules (codes used in `module` filters):
  DEV  Airport Development News (flagship)
  CAL  Calendar of Events
  MGT  Management, Ownership & Finance
  OPS  Airport Operations News
  CON  Consultant & Contractor News
  GSE  Ground Support Equipment
  ATC  Air Traffic Services
  MRO  Maintenance Base & FBO News
  AIT  Airport Information Technology

Common response envelope:
  { "data": <T | T[]>, "meta"?: { "page", "limit", "total", "pages" } }

================================================================================
ENDPOINTS
================================================================================

GET /api/v1/editions
  Query: page (default 1), limit (default 20, max 50)
  Returns: list of published editions with executive-summary fields
    (summary, top_developments[], key_trends[], regional_highlights, key_metrics).

GET /api/v1/editions/latest
  Returns: the most recent published edition plus its full article list
    (id, module, headline, content, region, country, airports[], tags[],
     source_name, source_url, takeaways[], why_it_matters, sort_order).
  Use this when you want "what's in this week's newsletter".

GET /api/v1/editions/:number
  Path: :number is the issue number (e.g. 1267).
  Returns: same shape as /editions/latest but for a specific issue.

GET /api/v1/articles
  Query:
    q          full-text search (Postgres websearch syntax)
    module     module code (DEV, MGT, ...)
    region     substring match
    country    substring match
    tag        single tag — article must contain it
    edition    issue number
    page, limit (default 20, max 100)
  Returns: paginated articles + linked edition_number / publish_date.

GET /api/v1/articles/:id
  Returns: single article (UUID id) with takeaways, why_it_matters, source.

GET /api/v1/search
GET /api/v1/search?q=...
POST /api/v1/search   { ...same params as JSON }
  This is the SAME search the in-app archive page uses.
  Query / body params:
    q                   keyword query (websearch FTS)
    module              module code
    region              exact region name
    year                "2024", "2025", ... (filters by edition publish_date)
    tag                 single required tag (must contain)
    any_tags            comma-separated list (article must contain at least one)
    any_regions         comma-separated list (OR over regions)
    any_modules         comma-separated list (OR over modules)
    exclude_tags        comma-separated list (article must NOT contain any)
    include_archived    "1" to also return archived (older imported) editions
    page, limit         pagination (default 30, max 100)
  Returns: { data: Article[], meta: { page, limit, total, pages } }
  Each article includes edition_number + publish_date so you can group by issue.

GET /api/v1/projects
  Airport projects database.
  Query: q, region, country, status (planned|ongoing|complete|cancelled|on_hold),
         type (substring match on project_type), min_value (USD integer),
         page, limit (default 50, max 100).
  Returns: paginated projects with airport_name, iata_code, country, region,
           project_type, value_usd, contractor, status, expected_completion_year,
           tags, last_seen_edition.

GET /api/v1/projects/:id
  Returns: full project + `articles` array of editions where it was mentioned.

GET /api/v1/projects/export
  Same filters as /projects. Returns text/csv (up to 1000 rows).

GET /api/v1/tenders                 [requires WAT add-on or Enterprise plan]
  Query: q, region, country, category, type (rfp|tender|framework|eoi),
         closed=1 (include expired), deadline_days (only show tenders closing
         within N days), sort (deadline_asc|deadline_desc|value_desc|published_desc),
         page, limit.

GET /api/v1/tenders/:id             [WAT or Enterprise]
GET /api/v1/tenders/export          [WAT or Enterprise]
  CSV export, same filters as list.

================================================================================
EXAMPLES
================================================================================

# 1. Latest newsletter content
curl -H "Authorization: Bearer mbg_live_..." \
     https://momberger.app/api/v1/editions/latest

# 2. All Capex articles in Africa from 2025
curl -H "Authorization: Bearer mbg_live_..." \
     "https://momberger.app/api/v1/search?q=capex&region=Africa&year=2025"

# 3. Ongoing terminal projects above $100M
curl -H "Authorization: Bearer mbg_live_..." \
     "https://momberger.app/api/v1/projects?status=ongoing&type=terminal&min_value=100000000"

# 4. Tenders closing in the next 30 days
curl -H "Authorization: Bearer mbg_live_..." \
     "https://momberger.app/api/v1/tenders?deadline_days=30"

# 5. Complex search via POST
curl -X POST -H "Authorization: Bearer mbg_live_..." \
  -H "Content-Type: application/json" \
  -d '{"q":"terminal","any_modules":["DEV","MGT"],"exclude_tags":["Cancelled"],"limit":50}' \
  https://momberger.app/api/v1/search

MCP Server

{
  "mcpServers": {
    "momberger": {
      "url": "https://momberger.app/api/mcp",
      "headers": {
        "Authorization": "Bearer mbg_live_…"
      }
    }
  }
}