What the Coronavirus Monitor API does and who it is for
Coronavirus Monitor aggregates COVID-19 data from several upstream sources — Johns Hopkins and the WHO are explicitly referenced — and normalizes that data into a consistent set of REST endpoints. The provider refreshes data on two cadences: some endpoints update every minute, others every ten minutes. That distinction matters for latency-sensitive use cases: if you need near-real-time global totals, you get them; if you are building a daily summary tool, the ten-minute refresh is more than adequate.
The target audience is fairly broad: developers building public-facing dashboards, journalists querying programmatic data for visualizations, researchers automating data collection, or product teams that want to embed pandemic context into a health or travel application. With an average success rate of 100% and a response latency of 765 ms, the API is stable and predictable enough for production use — though you should account for that sub-second latency in any synchronous UI flow.
Endpoint walkthrough
The API exposes 12 GET endpoints, all under the /coronavirus/ path. Here is a breakdown organized by scope:
Global and WHO data
/worldstat.php— Returns aggregate world totals. This is the single fastest query to get a global snapshot./who_latest_stat_by_country.php— WHO-sourced statistics looked up by country name./who_latest_stat_by_iso.php— Same WHO data, but keyed on ISO country code. Useful when you already hold ISO codes in your database and want to avoid string-matching country names./cases_by_country.php— Case data across countries, presumably from the provider's aggregated sources.
Country-level lookups (multiple identifier types)
The API offers three overlapping endpoints for per-country statistics, each accepting a different identifier:
/latest_stat_by_country.php— Country name string./latest_stat_by_iso_alpha_2.php— Two-letter ISO 3166-1 alpha-2 code (e.g.,US,DE)./latest_stat_by_iso_alpha_3.php— Three-letter ISO 3166-1 alpha-3 code (e.g.,USA,DEU).
This redundancy is genuinely convenient: it means you can integrate without a lookup table to convert between identifier formats.
Historical data
/cases_by_particular_country.php— Full history for a given country./history_by_particular_country_by_date.php— Narrows history to a specific date, useful for generating point-in-time reports or filling gaps in your own database.
United States detail
/united_states_cases.php— US national figures./johns_hopkins_latest_usa_statistic_by_state.php— State-level data sourced directly from Johns Hopkins. This is the most granular US endpoint and the one most useful for regional analysis.
Miscellaneous
/random_masks_usage_instructions.php— Returns mask usage guidance. Its practical relevance for most integrations is minimal, but it could serve as supplementary content in a health information app.
Pricing breakdown
The API uses four flat-rate monthly plans. All plans are billed per month with defined request quotas and overage rates:
| Plan | Monthly fee | Included requests | Overage per request |
|---|---|---|---|
| BASIC | $5 | 1,000 | $0.1000 |
| PRO | $10 | 10,000 | $0.0010 |
| ULTRA | $15 | 100,000 | $0.0001 |
| MEGA | $30 | Unlimited | — |
A few things stand out here. First, the BASIC overage rate of $0.10 per request is unusually high — 100 extra requests on BASIC would double your bill. If you expect any usage spikes, upgrading to PRO or ULTRA before hitting the BASIC ceiling is the pragmatic choice. Second, the jump from ULTRA (100,000 requests at $15) to MEGA (unlimited at $30) is a clean 2× in price. If your projected monthly usage is reliably above 100,000 requests, MEGA becomes cost-effective almost immediately given the vanishingly small ULTRA overage ($0.0001), but the unlimited ceiling eliminates budget unpredictability. For applications with volatile traffic — a dashboard that goes viral, for instance — MEGA is the safer default.
The provider also links to a freemium v2 of the API if you want to experiment without committing to a plan.
Practical use cases
Dashboard applications are the most obvious fit. The world totals endpoint combined with the per-country lookups gives you everything a live COVID-19 tracker needs without assembling data from multiple raw sources.
Research and data pipelines benefit from the historical endpoints. Scheduled jobs can call /history_by_particular_country_by_date.php to backfill or incrementally update a local data store, keeping API consumption predictable and quota-friendly.
US state-level analysis is well-served by the Johns Hopkins state endpoint, which is more granular than most competing aggregators provide at this price point.
Content and media tools can use the WHO-attributed endpoints to pull figures they can cite with a named source, which matters for journalistic use.
Limitations and things to verify before integrating
The provider is transparent that this version of the API is treated as lower priority compared to the v2 paid tiers. For production applications where data freshness is critical, it is worth testing the actual update cadence of each endpoint rather than assuming the stated one-minute refresh applies universally.
Response shape documentation is not included in the available materials. Before building your data model, make exploratory calls and inspect the JSON structure, particularly for fields like recovered counts or active cases, which have historically been inconsistently reported across COVID data sources.
The 765 ms average latency is acceptable for background data fetching but may feel slow in synchronous, user-facing contexts. Cache responses on your side — given the 1-to-10-minute refresh cadence of the upstream data, serving a 60-second cached response to your users costs you nothing in data accuracy.
Finally, the BASIC plan's steep overage rate means you should instrument your request count from day one. A simple counter or your platform's built-in usage dashboard will prevent surprise charges.
Getting started
The API is available on the RapidAPI marketplace. Authentication follows the standard RapidAPI header pattern, so if you have used other APIs on that platform the integration pattern will be familiar. Start with /worldstat.php to confirm connectivity and response structure, then move to the specific country or state endpoints relevant to your use case. The provider states that no user data is collected or stored, which simplifies any privacy review you might need to perform before shipping.
