Create or update an organization secret
Creates or updates an organization secret with an encrypted value. Encrypt your secret using LibSodium. For more information, see “Encrypting secrets for the REST API.”
Authenticated users must have collaborator access to a repository to create, update, or read secrets.
OAuth tokens and personal access tokens (classic) need the admin:org scope to use this endpoint. If the repository is private, OAuth tokens and personal access tokens (classic) need the repo scope to use this endpoint.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “ Path Parameters ”The organization name. The name is not case sensitive.
The name of the secret.
Request Body required
Section titled “ Request Body required ”object
Value for your secret, encrypted with LibSodium using the public key retrieved from the Get an organization public key endpoint.
ID of the key you used to encrypt the secret.
Which type of organization repositories have access to the organization secret. selected means only the repositories specified by selected_repository_ids can access the secret.
An array of repository ids that can access the organization secret. You can only provide a list of repository ids when the visibility is set to selected. You can manage the list of selected repositories using the List selected repositories for an organization secret, Set selected repositories for an organization secret, and Remove selected repository from an organization secret endpoints.
Examples
{ "encrypted_value": "c2VjcmV0", "key_id": "012345678912345678", "visibility": "selected", "selected_repository_ids": [ 1296269, 1296280 ]}Responses
Section titled “ Responses ”Response when creating a secret
An object without any properties.
object
Examples
nullResponse when updating a secret