Skip to main content
Skip to content
L’API REST est maintenant versionnée. Pour plus d’informations, consultez « À propos des versions de l’API ».

Points de terminaison d’API REST pour les propriétés personnalisées

Utilisez l’API REST afin de créer et gérer des propriétés personnalisées pour une organisation.

À propos des propriétés personnalisées

Vous pouvez utiliser l’API REST afin de créer et gérer des propriétés personnalisées pour une organisation. Vous pouvez utiliser des propriétés personnalisées pour ajouter des métadonnées aux référentiels de votre organisation. Pour plus d’informations, consultez « Gestion des propriétés personnalisées pour les référentiels de votre organisation ».

Get registered app installations for external custom properties

Gets the registered GitHub App installations used to read and write external custom properties for an organization.

A GitHub App installation token will only be able to see its own registration info, whereas an authenticated user will be able to see all registrations for the organization.

To use this endpoint, the authenticated caller must have the organization_external_properties_for_repos:admin permission.

Jetons d'accès granulaires pour «Get registered app installations for external custom properties»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "External custom properties for repositories" organization permissions (admin)

Paramètres pour «Get registered app installations for external custom properties »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

Codes d’état de réponse HTTP pour «Get registered app installations for external custom properties »

Code de statutDescription
200

OK

403

Forbidden

404

Resource not found

422

Validation failed, or the endpoint has been spammed.

Exemples de code pour «Get registered app installations for external custom properties »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

get/orgs/{org}/properties/installations
curl -L \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/installations

Response

Status: 200
[ { "value": { "display_name": "Acme", "installation": { "id": 1 } } } ]

Register an app installation for external custom properties

Registers a GitHub App installation so it can read and write external custom properties for an organization, and assigns it a display name.

The display name must be 1 to 15 characters and contain only letters and numbers. Capitalization is preserved as entered.

An app installation can only be registered once, and its display name can't be changed afterward. Calling with an app installation that has already been registered returns a 422 response with an already_exists error code for installation_id. If the display name is already in use by another app installation in the organization, the response is 422 with an already_exists error code for display_name. An invalid display name also returns 422.

The app installation being registered must have write or admin permission for organization external custom properties for repositories. If it doesn't, the response is 422. This is the permission of the installation being registered, which isn't necessarily the caller.

Uninstalling the GitHub App unregisters it, and removes the external custom properties it created.

To use this endpoint, the authenticated caller must have the organization_external_properties_for_repos:admin permission.

Jetons d'accès granulaires pour «Register an app installation for external custom properties»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "External custom properties for repositories" organization permissions (admin)

Paramètres pour «Register an app installation for external custom properties »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

Paramètres du corps
Nom, Type, Description
installation_id integer

The unique identifier of the GitHub App installation to register for managing external custom properties. When authenticating as a GitHub App installation, this defaults to the authenticated installation and can be omitted. It is required for all other callers (users and fine-grained personal access tokens).

display_name string Requis

The display name for this app installation's external custom properties in the organization. Must be 1 to 15 characters and contain only letters and numbers. Capitalization is preserved as entered. This can't be changed after the app installation is registered.

Codes d’état de réponse HTTP pour «Register an app installation for external custom properties »

Code de statutDescription
201

Created

403

Forbidden

404

Resource not found

422

Validation failed, or the endpoint has been spammed.

Exemples de code pour «Register an app installation for external custom properties »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

post/orgs/{org}/properties/installations
curl -L \ -X POST \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/installations \ -d '{"installation_id":67890,"display_name":"Acme"}'

Response

Status: 201
{ "display_name": "Acme", "installation": { "id": 1 } }

Get all external custom properties for a GitHub App installation in an organization

Gets all external custom properties defined for the authenticated GitHub App installation on an organization.

To use this endpoint, the authenticated GitHub App must have the organization_external_properties_for_repos:read permission.

Jetons d'accès granulaires pour «Get all external custom properties for a GitHub App installation in an organization»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "External custom properties for repositories" organization permissions (read)

Paramètres pour «Get all external custom properties for a GitHub App installation in an organization »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

Codes d’état de réponse HTTP pour «Get all external custom properties for a GitHub App installation in an organization »

Code de statutDescription
200

OK

403

Forbidden

404

Resource not found

422

Validation failed, or the endpoint has been spammed.

Exemples de code pour «Get all external custom properties for a GitHub App installation in an organization »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

get/orgs/{org}/properties/installations/schema
curl -L \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/installations/schema

Response

Status: 200
[ { "property_name": "environment" }, { "property_name": "business_unit" } ]

Create or update external custom property values for organization repositories

Create new or update existing external custom property values for repositories in a batch that belong to an organization. Each target repository will have its external custom property values updated to match the values provided in the request.

A maximum of 30 repositories can be updated in a single request.

Using a value of null for an external custom property will remove or 'unset' the property value from the repository.

To use this endpoint, the authenticated GitHub App must have the organization_external_properties_for_repos:write permission.

Jetons d'accès granulaires pour «Create or update external custom property values for organization repositories»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "External custom properties for repositories" organization permissions (write)

Paramètres pour «Create or update external custom property values for organization repositories »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

Paramètres du corps
Nom, Type, Description
repository_names array of strings Requis

The names of repositories that the external custom property values will be applied to.

properties array of objects Requis

List of external custom property names and associated values to apply to the repositories.

Nom, Type, Description
property_name string Requis

The name of the property

value null or string or array Requis

The value assigned to the property

Codes d’état de réponse HTTP pour «Create or update external custom property values for organization repositories »

Code de statutDescription
204

No Content when external custom property values are successfully created or updated

403

Forbidden

404

Resource not found

422

Validation failed, or the endpoint has been spammed.

Exemples de code pour «Create or update external custom property values for organization repositories »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

patch/orgs/{org}/properties/installations/values
curl -L \ -X PATCH \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/installations/values \ -d '{"repository_names":["Hello-World","octo-repo"],"properties":[{"property_name":"environment","value":"production"},{"property_name":"service","value":"web"},{"property_name":"team","value":"octocat"}]}'

No Content when external custom property values are successfully created or updated

Status: 204

Create or update external custom property values for a property across organization repositories

Create new or update existing external custom property values for a single named property across repositories that belong to an organization.

Up to 100 repository values can be updated in a single request. Repositories not included in the request are left unchanged.

Using a value of null for a repository will remove or 'unset' the property value for that repository. A request that only contains null values for a property that does not yet exist is a no-op.

To use this endpoint, the authenticated GitHub App must have the organization_external_properties_for_repos:write permission.

Jetons d'accès granulaires pour «Create or update external custom property values for a property across organization repositories»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "External custom properties for repositories" organization permissions (write)

Paramètres pour «Create or update external custom property values for a property across organization repositories »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

property_name string Requis

The name of the external custom property

Paramètres du corps
Nom, Type, Description
repository_values array of objects Requis

The names of repositories and the values that the named external custom property will be set to.

Nom, Type, Description
repository_name string Requis

The name of the repository

value string or null Requis

The value assigned to the repository. Set to null to unset the value for this repository.

Codes d’état de réponse HTTP pour «Create or update external custom property values for a property across organization repositories »

Code de statutDescription
204

A header with no content is returned.

403

Forbidden

404

Resource not found

422

Validation failed, or the endpoint has been spammed.

Exemples de code pour «Create or update external custom property values for a property across organization repositories »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

patch/orgs/{org}/properties/installations/values/{property_name}
curl -L \ -X PATCH \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/installations/values/PROPERTY_NAME \ -d '{"repository_values":[{"repository_name":"Hello-World","value":"production"},{"repository_name":"octo-repo","value":null}]}'

A header with no content is returned.

Status: 204

Remove all external custom property values for a property across all organization repositories

Removes all external custom property values for a specified property name across all repositories that belong to an organization.

To use this endpoint, the authenticated GitHub App must have the organization_external_properties_for_repos:write permission.

Jetons d'accès granulaires pour «Remove all external custom property values for a property across all organization repositories»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "External custom properties for repositories" organization permissions (write)

Paramètres pour «Remove all external custom property values for a property across all organization repositories »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

property_name string Requis

The name of the external custom property

Codes d’état de réponse HTTP pour «Remove all external custom property values for a property across all organization repositories »

Code de statutDescription
204

A header with no content is returned.

403

Forbidden

404

Resource not found

422

Validation failed, or the endpoint has been spammed.

Exemples de code pour «Remove all external custom property values for a property across all organization repositories »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

delete/orgs/{org}/properties/installations/values/{property_name}
curl -L \ -X DELETE \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/installations/values/PROPERTY_NAME

A header with no content is returned.

Status: 204

Get all custom properties for an organization

Gets all custom properties defined for an organization. Organization members can read these properties.

Jetons d'accès granulaires pour «Get all custom properties for an organization»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "Custom properties" organization permissions (read)

Paramètres pour «Get all custom properties for an organization »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

Codes d’état de réponse HTTP pour «Get all custom properties for an organization »

Code de statutDescription
200

OK

403

Forbidden

404

Resource not found

Exemples de code pour «Get all custom properties for an organization »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

get/orgs/{org}/properties/schema
curl -L \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/schema

Response

Status: 200
[ { "property_name": "environment", "url": "https://api.github.com/orgs/github/properties/schema/environment", "source_type": "organization", "value_type": "single_select", "required": true, "default_value": "production", "description": "Prod or dev environment", "allowed_values": [ "production", "development" ], "values_editable_by": "org_actors", "require_explicit_values": true }, { "property_name": "service", "url": "https://api.github.com/orgs/github/properties/schema/service", "source_type": "organization", "value_type": "string" }, { "property_name": "team", "url": "https://api.github.com/orgs/github/properties/schema/team", "source_type": "organization", "value_type": "string", "description": "Team owning the repository" } ]

Create or update custom properties for an organization

Creates new or updates existing custom properties defined for an organization in a batch.

If the property already exists, the existing property will be replaced with the new values. Missing optional values will fall back to default values, previous values will be overwritten. E.g. if a property exists with values_editable_by: org_and_repo_actors and it's updated without specifying values_editable_by, it will be updated to default value org_actors.

To use this endpoint, the authenticated user must be one of:

  • An administrator for the organization.
  • A user, or a user on a team, with the fine-grained permission of custom_properties_org_definitions_manager in the organization.

Jetons d'accès granulaires pour «Create or update custom properties for an organization»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "Custom properties" organization permissions (admin)

Paramètres pour «Create or update custom properties for an organization »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

Paramètres du corps
Nom, Type, Description
properties array of objects Requis

The array of custom properties to create or update.

Nom, Type, Description
property_name string Requis

The name of the property

url string

The URL that can be used to fetch, update, or delete info about this property via the API.

source_type string

The source type of the property

Peut être l'un des: organization, enterprise

value_type string Requis

The type of the value for the property

Peut être l'un des: string, single_select, multi_select, true_false, url

required boolean

Whether the property is required.

default_value null or string or array

Default value of the property

description string or null

Short description of the property

allowed_values array of strings or null

An ordered list of the allowed values of the property. The property can have up to 200 allowed values.

values_editable_by string or null

Who can edit the values of the property

Peut être l'un des: org_actors, org_and_repo_actors, null

require_explicit_values boolean

Whether setting properties values is mandatory

Codes d’état de réponse HTTP pour «Create or update custom properties for an organization »

Code de statutDescription
200

OK

403

Forbidden

404

Resource not found

Exemples de code pour «Create or update custom properties for an organization »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

patch/orgs/{org}/properties/schema
curl -L \ -X PATCH \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/schema \ -d '{"properties":[{"property_name":"environment","value_type":"single_select","required":true,"default_value":"production","description":"Prod or dev environment","allowed_values":["production","development"],"values_editable_by":"org_actors"},{"property_name":"service","value_type":"string"},{"property_name":"team","value_type":"string","description":"Team owning the repository"}]}'

Response

Status: 200
[ { "property_name": "environment", "url": "https://api.github.com/orgs/github/properties/schema/environment", "source_type": "organization", "value_type": "single_select", "required": true, "default_value": "production", "description": "Prod or dev environment", "allowed_values": [ "production", "development" ], "values_editable_by": "org_actors", "require_explicit_values": true }, { "property_name": "service", "url": "https://api.github.com/orgs/github/properties/schema/service", "source_type": "organization", "value_type": "string" }, { "property_name": "team", "url": "https://api.github.com/orgs/github/properties/schema/team", "source_type": "organization", "value_type": "string", "description": "Team owning the repository" } ]

Get a custom property for an organization

Gets a custom property that is defined for an organization. Organization members can read these properties.

Jetons d'accès granulaires pour «Get a custom property for an organization»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "Custom properties" organization permissions (read)

Paramètres pour «Get a custom property for an organization »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

custom_property_name string Requis

The custom property name

Codes d’état de réponse HTTP pour «Get a custom property for an organization »

Code de statutDescription
200

OK

403

Forbidden

404

Resource not found

Exemples de code pour «Get a custom property for an organization »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

get/orgs/{org}/properties/schema/{custom_property_name}
curl -L \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/schema/CUSTOM_PROPERTY_NAME

Response

Status: 200
{ "property_name": "environment", "url": "https://api.github.com/orgs/github/properties/schema/environment", "source_type": "organization", "value_type": "single_select", "required": true, "default_value": "production", "description": "Prod or dev environment", "allowed_values": [ "production", "development" ] }

Create or update a custom property for an organization

Creates a new or updates an existing custom property that is defined for an organization.

To use this endpoint, the authenticated user must be one of:

  • An administrator for the organization.
  • A user, or a user on a team, with the fine-grained permission of custom_properties_org_definitions_manager in the organization.

Jetons d'accès granulaires pour «Create or update a custom property for an organization»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "Custom properties" organization permissions (admin)

Paramètres pour «Create or update a custom property for an organization »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

custom_property_name string Requis

The custom property name

Paramètres du corps
Nom, Type, Description
value_type string Requis

The type of the value for the property

Peut être l'un des: string, single_select, multi_select, true_false, url

required boolean

Whether the property is required.

default_value null or string or array

Default value of the property

description string or null

Short description of the property

allowed_values array of strings or null

An ordered list of the allowed values of the property. The property can have up to 200 allowed values.

values_editable_by string or null

Who can edit the values of the property

Peut être l'un des: org_actors, org_and_repo_actors, null

require_explicit_values boolean

Whether setting properties values is mandatory

Codes d’état de réponse HTTP pour «Create or update a custom property for an organization »

Code de statutDescription
200

OK

403

Forbidden

404

Resource not found

Exemples de code pour «Create or update a custom property for an organization »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

put/orgs/{org}/properties/schema/{custom_property_name}
curl -L \ -X PUT \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/schema/CUSTOM_PROPERTY_NAME \ -d '{"value_type":"single_select","required":true,"default_value":"production","description":"Prod or dev environment","allowed_values":["production","development"]}'

Response

Status: 200
{ "property_name": "environment", "url": "https://api.github.com/orgs/github/properties/schema/environment", "source_type": "organization", "value_type": "single_select", "required": true, "default_value": "production", "description": "Prod or dev environment", "allowed_values": [ "production", "development" ] }

Remove a custom property for an organization

Removes a custom property that is defined for an organization.

To use this endpoint, the authenticated user must be one of:

  • An administrator for the organization.
  • A user, or a user on a team, with the fine-grained permission of custom_properties_org_definitions_manager in the organization.

Jetons d'accès granulaires pour «Remove a custom property for an organization»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "Custom properties" organization permissions (admin)

Paramètres pour «Remove a custom property for an organization »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

custom_property_name string Requis

The custom property name

Codes d’état de réponse HTTP pour «Remove a custom property for an organization »

Code de statutDescription
204

A header with no content is returned.

403

Forbidden

404

Resource not found

Exemples de code pour «Remove a custom property for an organization »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

delete/orgs/{org}/properties/schema/{custom_property_name}
curl -L \ -X DELETE \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/schema/CUSTOM_PROPERTY_NAME

A header with no content is returned.

Status: 204

List custom property values for organization repositories

Lists organization repositories with all of their custom property values. Organization members can read these properties.

Jetons d'accès granulaires pour «List custom property values for organization repositories»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "Custom properties" organization permissions (read)

Paramètres pour «List custom property values for organization repositories »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

Paramètres de requête
Nom, Type, Description
per_page integer

The number of results per page (max 100). For more information, see "Using pagination in the REST API."

Par défaut: 30

page integer

The page number of the results to fetch. For more information, see "Using pagination in the REST API."

Par défaut: 1

repository_query string

Finds repositories in the organization with a query containing one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub Enterprise Cloud. The REST API supports the same qualifiers as the web interface for GitHub Enterprise Cloud. To learn more about the format of the query, see Constructing a search query. See "Searching for repositories" for a detailed list of qualifiers.

Codes d’état de réponse HTTP pour «List custom property values for organization repositories »

Code de statutDescription
200

OK

403

Forbidden

404

Resource not found

Exemples de code pour «List custom property values for organization repositories »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

get/orgs/{org}/properties/values
curl -L \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/values

Response

Status: 200
[ { "repository_id": 1296269, "repository_name": "Hello-World", "repository_full_name": "octocat/Hello-World", "properties": [ { "property_name": "environment", "value": "production" }, { "property_name": "service", "value": "web" }, { "property_name": "team", "value": "octocat" } ] } ]

Create or update custom property values for organization repositories

Create new or update existing custom property values for repositories in a batch that belong to an organization. Each target repository will have its custom property values updated to match the values provided in the request.

A maximum of 30 repositories can be updated in a single request.

Using a value of null for a custom property will remove or 'unset' the property value from the repository.

To use this endpoint, the authenticated user must be one of:

  • An administrator for the organization.
  • A user, or a user on a team, with the fine-grained permission of custom_properties_org_values_editor in the organization.

Jetons d'accès granulaires pour «Create or update custom property values for organization repositories»

Ce point de terminaison fonctionne avec les types de tokens à granularité fine suivants:

Le token à granularité fine doit disposer de l’ensemble d’autorisations suivant:

  • "Custom properties" organization permissions (write)

Paramètres pour «Create or update custom property values for organization repositories »

En-têtes
Nom, Type, Description
accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès
Nom, Type, Description
org string Requis

The organization name. The name is not case sensitive.

Paramètres du corps
Nom, Type, Description
repository_names array of strings Requis

The names of repositories that the custom property values will be applied to.

properties array of objects Requis

List of custom property names and associated values to apply to the repositories.

Nom, Type, Description
property_name string Requis

The name of the property

value null or string or array Requis

The value assigned to the property

Codes d’état de réponse HTTP pour «Create or update custom property values for organization repositories »

Code de statutDescription
204

No Content when custom property values are successfully created or updated

403

Forbidden

404

Resource not found

422

Validation failed, or the endpoint has been spammed.

Exemples de code pour «Create or update custom property values for organization repositories »

Si vous accédez à GitHub à GHE.com, remplacez api.github.com par le sous-domaine dédié de votre entreprise à api.SUBDOMAIN.ghe.com.

Exemple de requête

patch/orgs/{org}/properties/values
curl -L \ -X PATCH \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2026-03-10" \ https://api.github.com/orgs/ORG/properties/values \ -d '{"repository_names":["Hello-World","octo-repo"],"properties":[{"property_name":"environment","value":"production"},{"property_name":"service","value":"web"},{"property_name":"team","value":"octocat"}]}'

No Content when custom property values are successfully created or updated

Status: 204