Add scan_type query param to full scan API#64
Merged
Merged
Add scan_type query param to full scan API#64
Conversation
…asics' to support different scan types when creating full scans. The scan_type parameter is passed as a query parameter in the fullscans.post and fullscans.archive methods.
|
🚀 Preview package published! Install with: pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple socketdev==3.0.29.dev1 |
Nolan Lawson (nolanlawson)
approved these changes
Jan 20, 2026
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
2 participants
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.
NOTICE: The currently deployed version of the Socket backend does not support this change. I will update the Socket CLI and Socket Basics to use the scan type once the Socket backend is deployed.
Add ScanType enum with values 'socket', 'socket_tier1', and 'socket_basics' to support different scan types when creating full scans.
Why?
This change allows us to distinguish Tier 1 scans from regular full scans, and is a requirement for proper ingestion of Tier 1 alerts into organization-wide alerts.
Public Changelog
N/A