Skip to content

docs!: single external timestamp (delivery, OpticOdds-parity) — OpenAPI 3.0.0 (SHA-1048)#257

Merged
Mlaz-code merged 1 commit into
mainfrom
fix/timestamp-canonical-field
Jun 2, 2026
Merged

docs!: single external timestamp (delivery, OpticOdds-parity) — OpenAPI 3.0.0 (SHA-1048)#257
Mlaz-code merged 1 commit into
mainfrom
fix/timestamp-canonical-field

Conversation

@Mlaz-code

Copy link
Copy Markdown
Collaborator

BREAKING — OpenAPI 3.0.0

The Odds response exposes a single timestamp field; odds_changed_at, last_seen_at, and wire_received_at are removed. timestamp is the delivery / last-refreshed stamp (advances every ingest cycle — feed-freshness, matching OpticOdds' timestamp), not a price-last-changed time. SharpAPI no longer exposes a "when the price moved" field. Mirrors sharp-api-go #751 (deploy together).

Changes

  • public/openapi.json: Odds schema → single timestamp (delivery description); removed the 3 fields; info.version 2.3.0 → 3.0.0 + CHANGELOG entry. FutureOdds/Splits timestamp/ts untouched.
  • mdx × 4 langs (en/es/pt-BR/de): field tables collapsed to one timestamp row; example bodies updated; concept page pinnacle-odds-changed-at repurposed to explain timestamp (slug kept so cross-links don't 404; anchor text + _meta.js label updated); migration <Callout> on odds.mdx. Also removed the phantom all_books[].timestamp (the API's per-book all_books[] entries carry no timestamp).
  • Remaining odds_changed_at/last_seen_at/wire_received_at mentions are intentional — migration callouts + the concept-page explanation only.

Notes

  • Pre-existing all_books[] doc gaps (phantom line, missing sportsbook) are out of scope — separate accuracy pass.

Refs SHA-1048
Type: docs

🤖 Generated with Claude Code

…erse #256 (SHA-1048)

BREAKING (OpenAPI 3.0.0): the Odds response exposes a single `timestamp` field;
`odds_changed_at`, `last_seen_at`, and `wire_received_at` are removed. `timestamp`
is the delivery / last-refreshed stamp (advances every ingest cycle — feed
freshness, matching OpticOdds' `timestamp`), NOT a price-last-changed time;
SharpAPI no longer exposes a when-the-price-moved field. Mirrors sharp-api-go #751.

- openapi.json: Odds schema → single `timestamp` (delivery description); removed
  the 3 fields; info.version 2.3.0 → 3.0.0 + CHANGELOG entry. FutureOdds/Splits
  `timestamp`/`ts` untouched.
- mdx × 4 langs (en/es/pt-BR/de): field tables collapsed to one `timestamp` row;
  examples updated; cross-links to the concept page kept (anchor text → `timestamp`);
  concepts/pinnacle-odds-changed-at repurposed to explain `timestamp` (slug kept) +
  _meta.js label; migration callout on odds.mdx. Removed the phantom
  `all_books[].timestamp` (the API's per-book entries carry no timestamp).
- Residual `odds_changed_at`/`last_seen_at`/`wire_received_at` mentions are
  intentional (migration callouts + concept-page explanation only).

Refs SHA-1048
Type: docs

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Mlaz-code Mlaz-code merged commit 80e1c04 into main Jun 2, 2026
1 check passed
@Mlaz-code Mlaz-code deleted the fix/timestamp-canonical-field branch June 2, 2026 16:14
@Mlaz-code

Copy link
Copy Markdown
Collaborator Author

Merge gate (auto-classified): gate=fixes-issue — auto-classified by the gate-log enforcer (5min after merge, no Merge gate: audit comment found). Reviewer agent: please correct if wrong by replying with Merge gate: gate=<correct-word> — <evidence>. The audit log keys on the first such token; your correction overrides this auto-classified guess.

Posted by scripts/gate-log-enforcer.py because instruction-level rules about the gate= template aren't binding (0/N adoption); structural enforcement fills the log either way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant