docs(api): remove socks5_proxy from scan, retest, scan config and automation requests - #245
Merged
Merged
Conversation
…omation request bodies platform-backend now rejects a non-empty socks5_proxy with 400 on these endpoints and no longer returns stored values; static egress is configured by ProjectDiscovery.
ehsandeep
approved these changes
Oct 2, 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
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.
Removes
socks5_proxyfrom the public API reference request bodies (retest, scan create, ScanConfig, ScanConfigUpdateItem, AutomationScanData).platform-backend now rejects a non-empty
socks5_proxywith 400 on these endpoints (projectdiscovery/platform-backend#1666): static egress is configured by ProjectDiscovery, not supplied by the customer.retest-vulnerability.mdxrenders from the spec, so no page edit was needed.Merge after platform-backend#1666 is deployed.