Skip to contentAPILayer: production APIs with free plansExplore APILayer
WhatsApp Rate Cards logo

Is WhatsApp Rate Cards API down?

Current status, daily uptime history and troubleshooting for the WhatsApp Rate Cards API (Open Data).

No, WhatsApp Rate Cards is up

WhatsApp Rate Cards answered our last daily check (Nov 15, 2026, 13:58 UTC) in 1786 ms with HTTP 200.

Checking WhatsApp Rate Cards now…

Sending a request from our server.

WhatsApp Rate Cards API uptime history

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

We check WhatsApp Rate Cards's listed URL (https://github.com/tobachat/whatsapp-api-rates#json) once a day. History started when WhatsApp Rate Cards was first checked, so new entries show fewer than 30 days.

WhatsApp Rate Cards 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. If it works from one network but not another, check firewalls, VPNs and regional blocks.
  3. Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.

Open Data APIs up at their last check

  1. 1Big Data Explained logo

    Big Data Explained API

    Online · 1065 ms

    Cloud data warehouse list prices, read daily from AWS and Azure pricing APIs, with price history.

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

    BTU Graph API

    Online · 1008 ms

    Source-reviewed energy company knowledge graph and directory exports.

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

    Caliber API

    Online · 1185 ms

    Which red dot optics fit which pistols, each fit cited to a maker or retailer.

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

    CollegeCalcAI API

    Online · 969 ms

    US college admission chance estimates and admissions data for 1,100+ colleges.

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

    EOSL API

    Online · 963 ms

    Hardware end-of-sale and end-of-service-life dates by part number, source-linked.

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

Compare all WhatsApp Rate Cards alternatives · APIs down right now

WhatsApp Rate Cards API status FAQ

Is WhatsApp Rate Cards API down right now?

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

How do you check whether WhatsApp Rate Cards API is up?

Once a day our checker requests WhatsApp Rate Cards's listed URL (https://github.com/tobachat/whatsapp-api-rates#json) 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 WhatsApp Rate Cards API?

WhatsApp Rate Cards answered 100% of our last 8 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 WhatsApp Rate Cards API is down?

Free Open Data APIs that were up at their last check include Big Data Explained, BTU Graph, Caliber. See the full list of WhatsApp Rate Cards alternatives for a comparison.

Why does WhatsApp Rate Cards 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. If it works from one network but not another, check firewalls, VPNs and regional blocks. Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.