# Build on WxAlerts

> Poll the REST API or subscribe to the live MQTT feeds, with and without an API key.

Developers · Overview · https://wxalerts.org/docs/developers/

Base URL: `https://api.wxalerts.org`

There are two ways to get weather data into your own software. The
[REST API](/docs/api/rest/) is plain HTTPS and JSON that you poll: ask what is
in effect at a point, in a box, or across the country. The
[MQTT feeds](/docs/developers/mqtt/alerts/) push NWS alerts and GOES lightning
to you the moment they are published, so a client that listens needs no
polling at all.

Most REST routes are public: no key needed, limited per address, and the same
endpoints this site calls from the browser. The rest are served only under
`/v1` with an [API key](/docs/developers/authentication/), which is also
accepted on the public routes, with `/v1` in front, to move the request off
your address's budget and onto the key's. A key-only route on the bare path
answers `401`. Browsers block calls from other websites (CORS allows only
wxalerts.org), so call the API from a server, script or app. The MQTT feeds
are public and read only.

  WxAlerts is not an official source of warnings, and neither is anything in
  this API. Data may be delayed, incomplete, inaccurate or absent, there is no
  uptime commitment, and derived products are experimental. If your client tells
  someone to shelter, evacuate or travel, point them at WEA, NOAA Weather Radio
  and the NWS as well; see [Terms §6](/terms/#life-safety), which is a material
  term of the license you are using these endpoints under.

None of it is exempt from the [Terms of Service](/terms/); the clauses that
decide what you may build are in [Terms for builders](/docs/developers/terms-for-builders/).