Repository navigation
Align History domain reads, entity responses and cursor lists - #16
Merged
Merged
Conversation
The public client lists domains and reads identifications through the domain-scoped History paths, and it no longer sends the retired unscoped search. Co-authored-by: Cursor <cursoragent@cursor.com>
Signup lookups now go to the domain History card, so the example reads SHIELDLABS_DOMAIN_ID. Co-authored-by: Cursor <cursoragent@cursor.com>
EgorMajj
approved these changes
Oct 29, 2026
EgorMajj
changed the title
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.
History reads use the public domain UUID and
/api/v1/domains/{domain_id}/history/{resource}/{resource_id}. Domain discovery and entity lists send the supported flat filters; non-zero offset is rejected before IO.Entity-card responses preserve ID, nested Risk Score, RFC3339 time, addresses, traffic and confirmed signal names. The original card remains in raw data. The new EntityPage returned by entity lists preserves aggregate fields and unavailable states and exposes the opaque next_page_token without a global total. Compatibility identification reads reject unavailable or invalid entity scores rather than inventing zero. README and changelog describe the list and compatibility contracts.
Validation: 594 tests including sync/async entity cards, null/unavailable aggregates, opaque cursors and FastAPI example; 98.34% coverage. Ruff and strict mypy pass.
Generated models were rebuilt from the vendored OpenAPI contract in the original change; CI rechecks generation and the supported runtime matrix. This PR changes source only and does not publish package versions.