docs!: single external timestamp (delivery, OpticOdds-parity) — OpenAPI 3.0.0 (SHA-1048)#257
Merged
Merged
Conversation
…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>
Collaborator
Author
|
Merge gate (auto-classified): gate=fixes-issue — auto-classified by the gate-log enforcer (5min after merge, no Posted by |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BREAKING — OpenAPI 3.0.0
The
Oddsresponse exposes a singletimestampfield;odds_changed_at,last_seen_at, andwire_received_atare removed.timestampis 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:Oddsschema → singletimestamp(delivery description); removed the 3 fields;info.version2.3.0 → 3.0.0 + CHANGELOG entry.FutureOdds/Splitstimestamp/tsuntouched.timestamprow; example bodies updated; concept pagepinnacle-odds-changed-atrepurposed to explaintimestamp(slug kept so cross-links don't 404; anchor text +_meta.jslabel updated); migration<Callout>onodds.mdx. Also removed the phantomall_books[].timestamp(the API's per-bookall_books[]entries carry no timestamp).odds_changed_at/last_seen_at/wire_received_atmentions are intentional — migration callouts + the concept-page explanation only.Notes
all_books[]doc gaps (phantomline, missingsportsbook) are out of scope — separate accuracy pass.Refs SHA-1048
Type: docs
🤖 Generated with Claude Code