Skip to content
Logistics & shipping

weatherbit.io

Weatherbit - Interactive Swagger UI Documentation sandbox and mock API

This an interactive version of the documentation for the Weatherbit API. The base URL for the API is [http://api.weatherbit.io/v2.0/](http://api.weatherbit.io/v2.0/) or [https://api.weatherbit.io/v2.0/](http://api.weatherbit.io/v2.0/). Below is the Swagger UI documentation for the API. All API requests require the `key` parameter. An Example for a 48 hour forecast for London, UK would be `http://a Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
47
Collections
-
Event types
-
Start this simulation
example request
curl https://your-weatherbit.slurry.io/v2.0/alerts?lat=123&lon=123 \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2.0.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 47.

  • GET/alerts?lat={lat}&lon={lon}
  • GET/bulk/files/{file}
  • GET/current/airquality?city={city}&country={country}
  • GET/current/airquality?city_id={city_id}
  • GET/current/airquality?lat={lat}&lon={lon}
  • GET/current/airquality?postal_code={postal_code}
  • GET/current?cities={cities}
  • GET/current?city={city}&country={country}
  • GET/current?city_id={city_id}
  • GET/current?lat={lat}&lon={lon}
  • GET/current?points={points}
  • GET/current?postal_code={postal_code}