GitHub: Update an organization
GitHub orgs.orgsUpdate: arguments, response, policy and SDK examples.
← Orgs operations · Get started
Operation github.orgs_update
Provider route: PATCH /orgs/{org}. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/github with npm, or alter-sdk-github with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { GitHubIntegration } from "@alter-ai/github";
async function execute(input: Parameters<GitHubIntegration["orgs"]["orgsUpdate"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new GitHubIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.orgs.orgsUpdate(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_github import GitHubIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = GitHubIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.orgs.orgs_update(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
path | object | Required within parent | Additional keys: not allowed |
path.org | string | Required within parent | |
body | object | Optional | |
body.advanced_security_enabled_for_new_repositories | boolean | Optional | Endpoint closing down notice. Please use [code security configurations](https://docs.github.com/rest/code-security/configurations) instead. Whether GitHub Advanced Security is automatically enabled for new repositories and repositories transferred to this organization. To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see “[Managing security managers in your organization](https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).” You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request. |
body.billing_email | string | Optional | Billing email address. This address is not publicized. |
body.blog | string | Optional | |
body.company | string | Optional | The company name. |
body.default_repository_permission | string | Optional | Default permission level members have for organization repositories. Default: read One of: read, write, admin, none |
body.dependabot_alerts_enabled_for_new_repositories | boolean | Optional | Endpoint closing down notice. Please use [code security configurations](https://docs.github.com/rest/code-security/configurations) instead. Whether Dependabot alerts are automatically enabled for new repositories and repositories transferred to this organization. To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see “[Managing security managers in your organization](https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).” You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request. |
body.dependabot_security_updates_enabled_for_new_repositories | boolean | Optional | Endpoint closing down notice. Please use [code security configurations](https://docs.github.com/rest/code-security/configurations) instead. Whether Dependabot security updates are automatically enabled for new repositories and repositories transferred to this organization. To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see “[Managing security managers in your organization](https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).” You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request. |
body.dependency_graph_enabled_for_new_repositories | boolean | Optional | Endpoint closing down notice. Please use [code security configurations](https://docs.github.com/rest/code-security/configurations) instead. Whether dependency graph is automatically enabled for new repositories and repositories transferred to this organization. To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see “[Managing security managers in your organization](https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).” You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request. |
body.deploy_keys_enabled_for_repositories | boolean | Optional | Controls whether or not deploy keys may be added and used for repositories in the organization. |
body.description | string | Optional | The description of the company. The maximum size is 160 characters. |
body.email | string | Optional | The publicly visible email address. |
body.has_organization_projects | boolean | Optional | Whether an organization can use organization projects. |
body.has_repository_projects | boolean | Optional | Whether repositories that belong to the organization can use repository projects. |
body.location | string | Optional | The location. |
body.members_allowed_repository_creation_type | string | Optional | Specifies which types of repositories non-admin organization members can create. `private` is only available to repositories that are part of an organization on GitHub Enterprise Cloud. Note: This parameter is closing down and will be removed in the future. Its return value ignores internal repositories. Using this parameter overrides values set in `members_can_create_repositories`. See the parameter deprecation notice in the operation description for details. One of: all, private, none |
body.members_can_create_internal_repositories | boolean | Optional | Whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. For more information, see “[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)” in the GitHub Help documentation. |
body.members_can_create_pages | boolean | Optional | Whether organization members can create GitHub Pages sites. Existing published sites will not be impacted. Default: true |
body.members_can_create_private_pages | boolean | Optional | Whether organization members can create private GitHub Pages sites. Existing published sites will not be impacted. Default: true |
body.members_can_create_private_repositories | boolean | Optional | Whether organization members can create private repositories, which are visible to organization members with permission. For more information, see “[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)” in the GitHub Help documentation. |
body.members_can_create_public_pages | boolean | Optional | Whether organization members can create public GitHub Pages sites. Existing published sites will not be impacted. Default: true |
body.members_can_create_public_repositories | boolean | Optional | Whether organization members can create public repositories, which are visible to anyone. For more information, see “[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)” in the GitHub Help documentation. |
body.members_can_create_repositories | boolean | Optional | Whether of non-admin organization members can create repositories. Note: A parameter can override this parameter. See `members_allowed_repository_creation_type` in this table for details. Default: true |
body.members_can_fork_private_repositories | boolean | Optional | Whether organization members can fork private organization repositories. Default: false |
body.name | string | Optional | The shorthand name of the company. |
body.secret_scanning_enabled_for_new_repositories | boolean | Optional | Endpoint closing down notice. Please use [code security configurations](https://docs.github.com/rest/code-security/configurations) instead. Whether secret scanning is automatically enabled for new repositories and repositories transferred to this organization. To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see “[Managing security managers in your organization](https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).” You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request. |
body.secret_scanning_push_protection_custom_link | string | Optional | If `secret_scanning_push_protection_custom_link_enabled` is true, the URL that will be displayed to contributors who are blocked from pushing a secret. |
body.secret_scanning_push_protection_enabled_for_new_repositories | boolean | Optional | Endpoint closing down notice. Please use [code security configurations](https://docs.github.com/rest/code-security/configurations) instead. Whether secret scanning push protection is automatically enabled for new repositories and repositories transferred to this organization. To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see “[Managing security managers in your organization](https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).” You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request. |
body.twitter_username | string | Optional | The Twitter username of the company. |
body.web_commit_signoff_required | boolean | Optional | Whether contributors to organization repositories are required to sign off on commits they make through GitHub’s web interface. Default: false |
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | Model | Root | Expand Get an organization — response body |
Referenced models: Get an organization — response body
Schemas
Section titled “Schemas”1 more schema is linked from the tables above, on the schema pages.
Get an organization — response body — plan
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
filled_seats | JSON | Optional | |
filled_seats (anyOf 1) | integer | Alternative | |
filled_seats (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
name | string | Required within parent | |
private_repos | JSON | Required within parent | |
private_repos (anyOf 1) | integer | Alternative | |
private_repos (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
seats | JSON | Optional | |
seats (anyOf 1) | integer | Alternative | |
seats (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
space | JSON | Required within parent | |
space (anyOf 1) | integer | Alternative | |
space (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: github.orgs_update. Catalog operation: orgs/update. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.
Pinned headers: {"X-GitHub-Api-Version": "2026-03-10", "User-Agent": "Alter", "Accept": "application/vnd.github+json"}