mocop
Browse · Docs · Guide · Analyze

Mukoko API

API by Mukoko · rest

api.mukoko.com is where each Mukoko app's public API lives, one namespace per app: Mukoko News at /v1/news, with Mukoko Weather and the others to follow at /v1/weather and so on. It is the consumer API: the Mukoko apps, the super app, their customers, partners and AI agents call it. The Nyuchi internal API (api.nyuchi.com) sits behind it and is for first-party services only. Weather answers (/v1/weather/*) keep the headers that say where the data came from (X-Cache, X-Weather-Provider, X-Current-Source, X-Weather-Blend, X-Enrichment, X-Fetched-At, X-AQ-Source) when they are present. If the weather data is unavailable you get 502 (upstream_error), 503 (upstream_unavailable, or not_configured on a deployment that is not set up for weather) or 504 (upstream_timeout). API keys. /v1/weather/* optionally accepts a Nyuchi API key (nyk_… with its nys_… secret) scoped for weather, in headers only, never in a URL: X-API-Key:…

Endpoint: https://api.mukoko.com/

Verification: observed. Source: crawl.

Capabilities (14)

  • Liveness check
  • This document as JSON
  • Latest articles
  • One article
  • Authors
  • Publishers
  • Current conditions hourly and daily forecast
  • Air quality
  • Nearest airports
  • Daily forecast
  • Nearest known place
  • Places
  • METAR and TAF
  • Search places
About · Contact · Privacy