Because ‘have they invaded yet?’ shouldn't require doomscrolling.
Read the same public YES, NO, or KINDA invasion answers shown on the site through a spreadsheet-ready CSV, cache-friendly JSON API, or RSS feed. This selected global conflict dataset is free, read-only, and requires no API key.
The CSV has one row per tracked conflict and preserves status, temperature applicability, timestamps, and the canonical briefing URL. It opens directly in spreadsheet and data-analysis tools.
curl -O https://havetheyinvadedyet.com/data/conflicts.csvThe unfiltered endpoint returns the current public summary for every tracked country pair.
curl -s https://havetheyinvadedyet.com/api/v1/conflicts.jsonPass a canonical conflict slug with slug. Topic aliases are also accepted by the feed resolver.
curl -s 'https://havetheyinvadedyet.com/api/v1/conflicts.json?slug=china-taiwan'CSV filters use the same canonical slugs as the JSON API, for example /data/conflicts.csv?slug=china-taiwan.
The top-level response includes snapshot freshness, source/fallback state, the applied filter, and a conflicts array. Each conflict summary includes the fields below plus its canonical briefing URL and provenance details.
This is a selected current conflict dataset, not a complete database of wars or armed conflicts. Each record covers one configured interstate invasion question and separates the categorical invasion status from the experimental escalation-temperature signal.
Assessments are derived from public reporting under the site's published methodology and editorial standards. Preserve the returned timestamps and canonical briefing URL so readers can inspect the current context and source links. For publication, see the citation guidance and stable conflict snapshots.
The HYIY-authored portions of this public dataset—including status classifications, temperatures, timestamps, descriptions, field definitions, and canonical identifiers—are available under the Creative Commons Attribution 4.0 International license (CC BY 4.0). You may share and adapt that material, including commercially, provided you give appropriate credit and indicate whether you made changes.
Suggested attribution: Have They Invaded Yet? conflict status dataset, https://havetheyinvadedyet.com/data, with the access date and the record's returned timestamps.
This license does not cover third-party article headlines or content, publisher names or marks, linked source materials, HYIY branding and logos, or the site's source code. Those remain subject to their respective owners' rights and terms. See the Terms of Use.
The global feed contains recent source-linked updates across the tracked set. Filter it with a conflict slug for one briefing, such as ?conflict=us-iran.
https://havetheyinvadedyet.com/feed.xml?conflict=us-iranResponses use shared caching and may be stale while the next refresh runs. Poll no more often than every three minutes, keep the returned timestamps visible, and link readers to the supplied canonical URL for context and sources.
Add a cache-friendly status badge to a README, blog, or conflict resource page. Keep the badge linked to its canonical briefing so readers can see the definitions, timestamps, context, and sources behind the answer. Topic aliases such as taiwan and canonical conflict slugs are accepted.
<a href="https://havetheyinvadedyet.com/taiwan">
<img src="https://havetheyinvadedyet.com/badge/taiwan"
width="440" height="52"
alt="Current China to Taiwan invasion status">
</a>Badges use the same public snapshot as the API and may be briefly stale while caches refresh. They are for attribution and orientation, not emergency alerts or professional risk decisions.
This is a small, selected, experimental, and partly automated tracker—not a comprehensive conflict dataset, scientific forecast, intelligence product, or emergency alert. Preserve the YES/NO/KINDA definitions and do not present temperature as a probability. See the methodology and editorial standards before building on the feed.