docs(odds): document offset cap, removed_truncated, since_clamped#192
Merged
Conversation
Companion to sharp-api-go PR #44. Documents the three new safety bounds on /odds and /odds/delta: - offset > 500 now returns 400 offset_too_large on both endpoints. /odds clients are directed to cursor= for deeper pagination; /odds/delta clients are directed to advance `since` to the previous response's `updated_at`. - /odds/delta responses may include removed_truncated: true when the `removed` array hits the 1000-entry cap, and since_clamped: true when the client's `since` was older than the 10-minute removal retention window. Both flags are optional — healthy polling clients (rolling `since` forward each call) never see them, which is called out in a new Polling note on the delta reference page. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Mlaz-code
added a commit
that referenced
this pull request
May 7, 2026
Companion to sharp-api-go PR #44. Documents the three new safety bounds on /odds and /odds/delta: - offset > 500 now returns 400 offset_too_large on both endpoints. /odds clients are directed to cursor= for deeper pagination; /odds/delta clients are directed to advance `since` to the previous response's `updated_at`. - /odds/delta responses may include removed_truncated: true when the `removed` array hits the 1000-entry cap, and since_clamped: true when the client's `since` was older than the 10-minute removal retention window. Both flags are optional — healthy polling clients (rolling `since` forward each call) never see them, which is called out in a new Polling note on the delta reference page. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Companion to sharp-api-go #44. Documents the three new safety bounds on
/oddsand/odds/delta.Pages updated
content/en/api-reference/odds.mdxoffsetrow now says "Must be ≤ 500" with pointer to cursor=content/en/api-reference/odds-delta.mdxoffsetrow updated with the 500 capServer-side context
Production nginx logs showed a small number of clients:
/oddsatoffset=4400..79800(1.5-2s each)/odds/deltawithsince=2h-ago(3.5 MB responses)The server-side caps in sharp-api-go #44 bound these pathologies; the docs here tell healthy clients what flags to ignore and misbehaving clients how to migrate.
Test plan
🤖 Generated with Claude Code