PUBLIC DATA ACCESS / NO AUTHENTICATION

API and RSS documentation

Use the read-only JSON API for structured data or subscribe to the RSS feed for the newest Daily Brief articles. No API key, account, cookie, or database session is required.

API version 1 US English and US Spanish Read-only

JSON API

Intelligence feed

The normalized local feed used by the Intelligence Desk. Supports ETag revalidation and a five-minute public cache.

https://internationalintelligence.org/en-US/api/feed/ Open JSON feed

RSS 2.0

Latest news feed

Up to 50 recent Daily Brief article entries with localized titles, summaries, dates, categories, and article URLs.

https://internationalintelligence.org/en-US/rss/ Open RSS feed

STATUS JSON

Publishing health

A redacted operational snapshot for source refreshes and Daily Brief publication. It never exposes credentials or provider responses.

https://internationalintelligence.org/en-US/api/status/ Open status JSON

ENDPOINT REFERENCE

Public endpoints

Method and route	Format	Purpose and caching
`GET /en-US/api/feed/`	`application/json`	Normalized intelligence items. Public cache: 300 seconds. Send If-None-Match with the previous ETag to receive HTTP 304 when unchanged.
`GET /en-US/api/status/`	`application/json`	Redacted source and Daily Brief health. Cache-Control is no-store because the state may change between requests.
`GET /en-US/rss/`	`application/rss+xml`	Localized RSS 2.0 feed containing up to 50 recent Daily Brief story pages. Public cache: 900 seconds with ETag support.
`GET /rss.xml`	`application/rss+xml`	English x-default machine-feed alias for feed readers that expect a root RSS URL.
`GET /openapi.json`	`application/json`	OpenAPI 3.1 description of the public read-only interfaces and response schemas.

QUICKSTART

Copy-ready examples

curl

curl --fail --silent --show-error \
  -H 'Accept: application/json' \
  'https://internationalintelligence.org/en-US/api/feed/'

Conditional request with ETag

curl --fail --silent --show-error \
  -H 'If-None-Match: "YOUR_PREVIOUS_ETAG"' \
  'https://internationalintelligence.org/en-US/api/feed/'

Plain JavaScript

const response = await fetch('/en-US/api/feed/', {
  headers: { Accept: 'application/json' }
});
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const feed = await response.json();
console.log(feed.items);

RSS subscription URL

https://internationalintelligence.org/en-US/rss/

DATA CONTRACT

Feed schema at a glance

The JSON feed is a local publication artifact. Source-specific payloads are normalized into a stable top-level envelope and source-aware item records.

schema_versionInteger contract version.

generated_atISO 8601 cache-generation time.

source_modeUsually seed or refreshed cache.

items[]Normalized source-aware records.

evidence_tierNumeric Evidence Ladder position.

confidenceVisible editorial confidence label.

Example response

{
    "schema_version": 1,
    "generated_at": "2026-07-24T09:15:00-05:00",
    "source_mode": "seed",
    "item_count": 10,
    "items": [
        {
            "id": "794212aa32e5bd2edf638d4c",
            "title": "Architecting public intelligence without exposing the reader",
            "summary": "A foundational report explains the server-side acquisition model, common evidence schema, official-record connectors, procurement workflow, and flat-host deployment pattern.",
            "url": "/en-US/research/architecting-public-intelligence/",
            "published_at": "2026-07-24T09:00:00-05:00",
            "source": "International Intelligence Research Desk",
            "topics": [
                "public-records",
                "privacy",
                "procurement",
                "surveillance"
            ],
            "evidence_tier": 6,
            "confidence": "Corroborated"
        }
    ]
}

RESPONSIBLE USE

Caching, provenance, and stability

No authentication is required for the documented read-only endpoints.
Honor Cache-Control and ETag headers instead of polling continuously.
Preserve item source names, evidence tiers, confidence labels, publication dates, and original-source links.
The API contains current and provisional material. Do not silently relabel it as settled historical fact.
The public interface is versioned independently from the site release. Breaking API changes require a new API contract version.