Skip to contentAPILayer: production APIs with free plansExplore APILayer
PourWire logo

Is PourWire API down?

Current status, daily uptime history and troubleshooting for the PourWire API (Government).

No, PourWire is up

PourWire answered our last daily check (Nov 15, 2026, 13:58 UTC) in 543 ms with HTTP 200.

Checking PourWire now…

Sending a request from our server.

PourWire API uptime history

30 days agoLatest check
Uptime
100% of 10 checks
Last check
Nov 15, 2026, 13:58 UTC
Response
543 ms · HTTP 200
Last up
Now

We check PourWire's listed URL (https://github.com/Tintin-Intellegence-Limited/us-liquor-license-applications#free-json-api) once a day. History started when PourWire was first checked, so new entries show fewer than 30 days.

PourWire API not working for you?

  1. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
  2. PourWire doesn't send CORS headers, so browsers block calls made directly from a web page. Call it from your server instead.
  3. If it works from one network but not another, check firewalls, VPNs and regional blocks.
  4. Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.

Government APIs up at their last check

  1. 1EU VAT Rates by Commodity Code logo

    EU VAT rates mapped to CN and CPA commodity codes, all 27 member states.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  2. 2MORVS logo

    MORVS API

    Online · 1121 ms

    Source-linked US regulatory and public records: SEC filings, enforcement actions, recalls.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  3. 3nu:legal Deutsches Recht logo

    German federal and state statutes and 640,000 court decisions as JSON, with citation links.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  4. 4Tollmint logo

    Tollmint API

    Online · 1163 ms

    Advertising, subscription, AI-disclosure and accessibility rules across the US, EU and UK.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  5. 5

    US Per Diem API

    Online · 660 ms

    GSA lodging and M&IE per diem rates for US cities by ZIP, state and fiscal year.

    • No API key needed
    • 100% uptime (30 days)
    • Returns JSON at its URL
    • Callable from the browser (CORS)
    No authHTTPSCORS

Compare all PourWire alternatives · APIs down right now

PourWire API status FAQ

Is PourWire API down right now?

PourWire answered our last daily check (Nov 15, 2026, 13:58 UTC) in 543 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether PourWire is responding at this moment.

How do you check whether PourWire API is up?

Once a day our checker requests PourWire's listed URL (https://github.com/Tintin-Intellegence-Limited/us-liquor-license-applications#free-json-api) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.

How reliable is PourWire API?

PourWire answered 100% of our last 10 daily checks. Above 99% is excellent for a free API; below 95% means you should cache responses and keep a fallback ready.

What can I use if PourWire API is down?

Free Government APIs that were up at their last check include EU VAT Rates by Commodity Code, MORVS, nu:legal Deutsches Recht. See the full list of PourWire alternatives for a comparison.

Why does PourWire API work for others but not for me?

A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. PourWire doesn't send CORS headers, so browsers block calls made directly from a web page. Call it from your server instead. If it works from one network but not another, check firewalls, VPNs and regional blocks.