GitHub REST API now supports managing secret scanning custom patterns
GitHub has introduced REST API endpoints for managing secret scanning custom patterns, allowing security teams to create, edit, and delete these rules programmatically. This feature is now generally available at the repository, organization, and enterprise levels for secret scanning customers. While core CRUD operations are available via API, dry runs and publishing still require the UI.
- →Manage secret scanning custom patterns via REST API
- →UI required for pattern publishing
- →Documentation available
Features (1) ›
- Manage secret scanning custom patterns via REST API
New REST API endpoints for GET, POST, PATCH, and DELETE operations on secret scanning custom patterns are now generally available. These endpoints allow for programmatic management of custom patterns at repository, organization, and enterprise levels.
Notes (2) ›
- UI required for pattern publishing
Creation, editing, and deletion of custom secret scanning patterns can be managed via the REST API. However, completing dry runs and the final publishing step still require using the GitHub UI.
- Documentation available
Further details on the new capabilities can be found in the GitHub changelog and the REST API documentation for secret scanning and custom patterns.
https://github.blog/changelog/2026-07-13-create-and-manage-secret-scanning-custom-patterns-via-rest-api
Related releases
- GitHub Copilot Deprecates Gemini 2.5 Pro and 3 Flash Models GitHub Changelog ·
- GitHub Copilot Enterprise Teams Model Policy Targeting in Public Preview GitHub Changelog ·
- npm restricts granular access token ability to bypass 2FA for sensitive actions GitHub Changelog ·
- GitHub Models officially retired GitHub Changelog ·
- GitHub Copilot VS Code Updates: Agents, Chat, UI, and Accessibility GitHub Changelog ·
- GitHub Actions: Reference same-repo workflows with self-repository syntax GitHub Changelog ·