# secret_scanning_validity_checks_enabled on PATCH /orgs/{} stops working

Calls to PATCH /orgs/{id}, body parameter secret_scanning_validity_checks_enabled on GitHub REST API stopped working on April 21, 2026.

On April 21, 2026, the GitHub REST API removed support for the body parameter secret_scanning_validity_checks_enabled on the PATCH /orgs/{id} endpoint. Calls using this parameter fail since that date because the field is no longer available. Developers must update scripts and integrations that read or write this setting.

## What to use instead

Use code security configurations (/orgs/{org}/code-security/configurations) and set a default configuration for new repositories.

- API: GitHub REST API (api.github.com)
- Kind: Parameter removal
- Announced: March 24, 2026
- Takes effect: April 21, 2026
- Calls after that day: fail
- Calls it hits: `PATCH /orgs/{id}`, `body parameter secret_scanning_validity_checks_enabled`
- Source: [Announcement](https://github.blog/changelog/2026-03-24-upcoming-deprecation-of-security-related-organization-api-fields)
- Verified: November 6, 2026, against GitHub REST API's own pages
- Page: https://www.okapi.bot/providers/github-rest-api/breaking-changes/secret-scanning-validity-checks-enabled-on-patch-orgs-stops-working/

## GitHub REST API's words

> Update any scripts or integrations that read or write these fields, as they’ll no longer be available after April 21, 2026.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent