Skip to content
Disclosed Capitol logo

Is Disclosed Capitol API down?

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

No, Disclosed Capitol is up

Disclosed Capitol answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1672 ms with HTTP 200.

Checking Disclosed Capitol now…

Sending a request from our server.

Disclosed Capitol API uptime history

30 days agoLatest check
Uptime
2 checks so far
Last check
Oct 24, 2026, 12:25 UTC
Response
1672 ms · HTTP 200
Last up
Now

We check Disclosed Capitol's listed URL (https://www.disclosedcapitol.com/data-files/api) once a day. History started when Disclosed Capitol was first checked, so new entries show fewer than 30 days.

Disclosed Capitol API not working for you?

  1. Disclosed Capitol needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
  2. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
  3. Disclosed Capitol doesn't send CORS headers, so browsers block calls made directly from a web page. Call it from your server instead.
  4. If it works from one network but not another, check firewalls, VPNs and regional blocks.
  5. 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. 1Bidledger logo

    Bidledger API

    Online · 279 ms

    Every open public tender in the European Union, rebuilt daily from the official TED data.

    • No API key needed
    • Fast: 279 ms response
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  2. 2Ayes and Noes logo

    Ayes and Noes API

    Online · 526 ms

    UK House of Commons MPs, parties and recorded votes.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  3. 3Brazil logo

    Brazil API

    Online · 504 ms

    Community driven API for Brazil Public Data.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  4. 4Election logo

    Election API

    Online · 962 ms

    Source-linked U.S. election and civic records with coverage limits.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  5. 5EU VAT Rates by Commodity Code logo

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

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS

Compare all Disclosed Capitol alternatives · APIs down right now

Disclosed Capitol API status FAQ

Is Disclosed Capitol API down right now?

Disclosed Capitol answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1672 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether Disclosed Capitol is responding at this moment.

How do you check whether Disclosed Capitol API is up?

Once a day our checker requests Disclosed Capitol's listed URL (https://www.disclosedcapitol.com/data-files/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.

What can I use if Disclosed Capitol API is down?

Free Government APIs that were up at their last check include Bidledger, Ayes and Noes, Brazil. See the full list of Disclosed Capitol alternatives for a comparison.

Why does Disclosed Capitol API work for others but not for me?

Disclosed Capitol needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. Disclosed Capitol doesn't send CORS headers, so browsers block calls made directly from a web page. Call it from your server instead.