Public data access

Free conflict status API and RSS feed

Read the same public YES, NO, or KINDA invasion answers shown on the site through a cache-friendly JSON API or RSS feed. Both surfaces are free, read-only, and require no API key.

Open JSON API Open RSS feed

Get every tracked conflict

The unfiltered endpoint returns the current public summary for every tracked country pair.

curl -s https://havetheyinvadedyet.com/api/v1/conflicts.json

Filter to one briefing

Pass 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'

Response fields

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.

status: YES, NO, or KINDA under this site’s editorial invasion threshold.
temperature: Experimental escalation-pressure score from 0–100, or null after a confirmed YES.
temperatureApplicable: Whether the temperature value is meaningful for the current status.
statusLine / description: Plain-language public context for the displayed answer.
sourceCheckedAtISO: When the public-source refresh last completed for that conflict.
statusReviewedAtISO: When the discrete editorial status was last reviewed, when available.
newestRelevantEvidenceAtISO: Timestamp of the newest relevant report retained in the public snapshot.
latestHeadlines: Up to five recent, source-linked headline records.

RSS for readers and automations

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-iran

Caching and responsible use

Responses 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.

Embed a live status badge

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.

Important limitations

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.