Full data overview
Status summary, forecast, signals, history and source metadata. A good first request for your app.
01 / ENDPOINTS
JSONAPI endpoints
Choose data for your use case to avoid fetching the same upstream announcements repeatedly.
Reset-related signals
Filter public updates for resets, plans, hints and quota news, preserving categories and verification status.
Reset announcement history
Recorded reset announcements. A completion announcement does not verify a local account's quota.
GET
/api/v1/tibo Tibo public updates
All valid recorded posts, including original text, publication time, links and collection mode.
GET
/api/health Service health
Check service and source availability for deployment probes and scheduled jobs.
Permanent post history
Permanently stored original posts and collection sources, with pagination. History before the first collection may be incomplete.
Experimental probability model
Returns the historical baseline, experimental adjustments and per-post impacts. Rules are uncalibrated; the original forecast API retains the upstream baseline.
Field:
/api/v1/overviewprobability_model → baseline / adjusted / factors / model_version / evaluated_attibo_history → total / persistent / complete_historyQUERY PARAMETERS
Filtering and pagination
Applies to the signals, resets and tibo list endpoints.
| Parameter | Description |
|---|---|
limit / offset | limit is 1–100, default 50; offset starts at 0. Use the returned next_offset for the next page. |
kind | kind accepts reported_completed, planned, hint, limits, banked, unclear, needs_context or other; type is a compatibility alias. |
q | Keyword search, up to 200 characters. |
from / to | UTC date range in YYYY-MM-DD format. |
List responses include items, count, total, limit, offset and next_offset.View a filtering example ↗
02 / READ THE RESPONSE
Check status before using the data.
| Field | Meaning |
|---|---|
available | Whether a usable snapshot is currently available. Show a clear empty state when it is unavailable. |
stale | Whether the data comes from an expired cache. Tell users about freshness when displaying cached records. |
generated_at | When this API response was generated. This is separate from post publication and collection times. |
channels | Records fetched_at, checked_at, availability and errors for each source. |
posts | Original text and URL, publication time, category and post verification status. |
quota_verified | Whether actual account quota was verified. A false value must not be displayed as 'quota restored'. |
tibo.mode | x_api, third_party_copy or unavailable distinguishes direct collection from third-party copies. |
Forecast fields probability_24h / probability_48h are percentages from 0 to 100. Show an unknown value when no forecast is available, rather than 0%.
03 / INTEGRATION
A minimal integration example.
GET endpoints require no authentication and support cross-origin requests.
const response = await fetch(
'https://codexreset-news.com/api/v1/overview',
{ headers: { Accept: 'application/json' } }
);
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const data = await response.json();
if (!data.available) {
// Show 'Data unavailable'; do not infer there was no reset.
} else {
const posts = data.tibo?.items ?? data.posts ?? [];
const cached = data.stale === true;
// Show original links and preserve third-party attribution.
}Collection refresh endpoints use separate authentication; the frontend needs no collection key.View current service status ↗
04 / COMPATIBILITY
Compatible with existing calls.
Legacy endpoints remain available. Use the versioned v1 endpoints for new integrations.