{
  "opencollection": "1.0.0",
  "info": {
    "name": "Atlassian Admin Account Add API",
    "version": "1.0.0"
  },
  "request": {
    "auth": {
      "type": "bearer",
      "token": "{{bearerToken}}"
    }
  },
  "items": [
    {
      "info": {
        "name": "Add",
        "type": "folder"
      },
      "items": [
        {
          "info": {
            "name": "Atlassian Add User to the Default Reviewers",
            "type": "http"
          },
          "http": {
            "method": "PUT",
            "url": "https://api.atlassian.com/repositories/:workspace/:repo_slug/default-reviewers/:target_username",
            "params": [
              {
                "name": "repo_slug",
                "value": "",
                "type": "path",
                "description": "This can either be the repository slug or the UUID of the repository,\nsurrounded by curly-braces, for example: `{repository UUID}`.\n"
              },
              {
                "name": "target_username",
                "value": "",
                "type": "path",
                "description": "This can either be the username or the UUID of the default reviewer,\nsurrounded by curly-braces, for example: `{account UUID}`.\n"
              },
              {
                "name": "workspace",
                "value": "",
                "type": "path",
                "description": "This can either be the workspace ID (slug) or the workspace UUID\nsurrounded by curly-braces, for example: `{workspace UUID}`.\n"
              }
            ],
            "auth": {
              "type": "oauth2",
              "flow": "authorization_code",
              "authorizationUrl": "https://auth.atlassian.com/authorize",
              "accessTokenUrl": "https://auth.atlassian.com/oauth/token",
              "credentials": {
                "clientId": "{{clientId}}",
                "clientSecret": "{{clientSecret}}"
              }
            }
          },
          "docs": "This API operation adds a specific user to the default reviewers list for a Bitbucket repository within a given workspace. By making a PUT request to the endpoint with the workspace identifier, repository slug, and target username, administrators can configure automatic reviewer assignments for pull requests in that repository. When a user is added as a default reviewer, they will be automatically included in the reviewer list whenever a new pull request is created in the repository, streamlinin"
        },
        {
          "info": {
            "name": "Atlassian Add Repository Deploy Key",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.atlassian.com/repositories/:workspace/:repo_slug/deploy-keys",
            "params": [
              {
                "name": "repo_slug",
                "value": "",
                "type": "path",
                "description": "This can either be the repository slug or the UUID of the repository,\nsurrounded by curly-braces, for example: `{repository UUID}`.\n"
              },
              {
                "name": "workspace",
                "value": "",
                "type": "path",
                "description": "This can either be the workspace ID (slug) or the workspace UUID\nsurrounded by curly-braces, for example: `{workspace UUID}`.\n"
              }
            ],
            "auth": {
              "type": "oauth2",
              "flow": "authorization_code",
              "authorizationUrl": "https://auth.atlassian.com/authorize",
              "accessTokenUrl": "https://auth.atlassian.com/oauth/token",
              "credentials": {
                "clientId": "{{clientId}}",
                "clientSecret": "{{clientSecret}}"
              }
            }
          },
          "docs": "This API operation allows you to add a new deploy key to a specific Bitbucket repository within a workspace. Deploy keys are SSH keys that grant read-only or read-write access to a repository, typically used for automated deployment processes or CI/CD pipelines. By making a POST request to this endpoint with the workspace identifier and repository slug, along with the required key details in the request body (such as the SSH public key and an optional label), you can programmatically register a "
        },
        {
          "info": {
            "name": "Atlassian Add New Ssh Key",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.atlassian.com/users/:selected_user/ssh-keys",
            "params": [
              {
                "name": "selected_user",
                "value": "",
                "type": "path",
                "description": "This can either be an Atlassian Account ID OR the UUID of the account,\nsurrounded by curly-braces, for example: `{account UUID}`.\n"
              }
            ],
            "body": {
              "type": "json",
              "data": "{}"
            },
            "auth": {
              "type": "oauth2",
              "flow": "authorization_code",
              "authorizationUrl": "https://auth.atlassian.com/authorize",
              "accessTokenUrl": "https://auth.atlassian.com/oauth/token",
              "credentials": {
                "clientId": "{{clientId}}",
                "clientSecret": "{{clientSecret}}"
              }
            }
          },
          "docs": "This API operation allows you to add a new SSH key to a specific Bitbucket user's account by making a POST request to the /users/{selected_user}/ssh-keys endpoint, where {selected_user} represents the username of the target account. The operation requires you to provide SSH key details in the request body, typically including the key content and an optional label for identification purposes. Once successfully added, the SSH key enables secure authentication for Git operations and other SSH-based"
        },
        {
          "info": {
            "name": "Atlassian Add the Specific User as a Default Reviewer for the Project",
            "type": "http"
          },
          "http": {
            "method": "PUT",
            "url": "https://api.atlassian.com/workspaces/:workspace/projects/:project_key/default-reviewers/:selected_user",
            "params": [
              {
                "name": "project_key",
                "value": "",
                "type": "path",
                "description": "The project in question. This can either be the actual `key` assigned\nto the project or the `UUID` (surrounded by curly-braces (`{}`)).\n"
              },
              {
                "name": "selected_user",
                "value": "",
                "type": "path",
                "description": "This can either be the username or the UUID of the default reviewer,\nsurrounded by curly-braces, for example: `{account UUID}`.\n"
              },
              {
                "name": "workspace",
                "value": "",
                "type": "path",
                "description": "This can either be the workspace ID (slug) or the workspace UUID\nsurrounded by curly-braces, for example: `{workspace UUID}`.\n"
              }
            ],
            "auth": {
              "type": "oauth2",
              "flow": "authorization_code",
              "authorizationUrl": "https://auth.atlassian.com/authorize",
              "accessTokenUrl": "https://auth.atlassian.com/oauth/token",
              "credentials": {
                "clientId": "{{clientId}}",
                "clientSecret": "{{clientSecret}}"
              }
            }
          },
          "docs": "This PUT operation adds a specified user as a default reviewer for a particular project within a Bitbucket workspace. By targeting the endpoint with the workspace slug, project key, and the selected user's identifier, it configures that user to be automatically added as a reviewer on all new pull requests created in the project. This helps streamline the code review process by ensuring designated team members are consistently included in pull request reviews without manual assignment, making it "
        },
        {
          "info": {
            "name": "Atlassian Add Labels to Content",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.atlassian.com/wiki/rest/api/content/:id/label",
            "params": [
              {
                "name": "id",
                "value": "",
                "type": "path",
                "description": "The ID of the content that will have labels added to it."
              }
            ],
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "This API operation allows you to add one or more labels to a specific piece of Confluence content by making a POST request to the endpoint with the content's unique identifier. Labels are metadata tags that help organize, categorize, and improve the discoverability of pages, blog posts, and other content within Confluence. When calling this endpoint, you must provide the content ID in the URL path and include an array of label objects in the request body, specifying properties such as the label "
        },
        {
          "info": {
            "name": "Atlassian Add Restrictions",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.atlassian.com/wiki/rest/api/content/:id/restriction",
            "params": [
              {
                "name": "id",
                "value": "",
                "type": "path",
                "description": "The ID of the content to add restrictions to."
              },
              {
                "name": "expand",
                "value": "",
                "type": "query",
                "description": "A multi-value parameter indicating which properties of the content\nrestrictions (returned in response) to expand.\n\n- `restrictions.user` returns the piece of content that the restrictions are\napplied to. Expanded by default.\n- `restrictions.group` returns the piece of content that the restrictions are\napplied to. Expanded by default.\n- `content` returns the piece of content that the restrictions are\napplied to."
              }
            ],
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "The Add Restrictions operation in the Atlassian Confluence Content API allows you to apply access controls to a specific piece of content by sending a POST request to /wiki/rest/api/content/{id}/restriction, where {id} represents the unique identifier of the content you want to restrict. This endpoint enables administrators and authorized users to define who can view or edit the content by specifying user accounts, groups, or both in the request payload. The restrictions can be applied at differ"
        },
        {
          "info": {
            "name": "Atlassian Add Group to Content Restriction",
            "type": "http"
          },
          "http": {
            "method": "PUT",
            "url": "https://api.atlassian.com/wiki/rest/api/content/:id/restriction/byOperation/:operationKey/group/:groupName",
            "params": [
              {
                "name": "id",
                "value": "",
                "type": "path",
                "description": "The ID of the content that the restriction applies to."
              },
              {
                "name": "operationKey",
                "value": "",
                "type": "path",
                "description": "The operation that the restriction applies to."
              },
              {
                "name": "groupName",
                "value": "",
                "type": "path",
                "description": "The name of the group to add to the content restriction."
              }
            ]
          },
          "docs": "The PUT operation on the Atlassian Confluence Content API endpoint `/wiki/rest/api/content/{id}/restriction/byOperation/{operationKey}/group/{groupName}` adds a specified group to an existing content restriction for a particular operation type. This allows administrators to grant a group access to perform specific operations (such as read, update, or delete) on restricted Confluence content by including the group in the restriction's allowed list. The endpoint requires three path parameters: the"
        },
        {
          "info": {
            "name": "Atlassian Add Group to Content Restriction",
            "type": "http"
          },
          "http": {
            "method": "PUT",
            "url": "https://api.atlassian.com/wiki/rest/api/content/:id/restriction/byOperation/:operationKey/byGroupId/:groupId",
            "params": [
              {
                "name": "id",
                "value": "",
                "type": "path",
                "description": "The ID of the content that the restriction applies to."
              },
              {
                "name": "operationKey",
                "value": "",
                "type": "path",
                "description": "The operation that the restriction applies to."
              },
              {
                "name": "groupId",
                "value": "",
                "type": "path",
                "description": "The groupId of the group to add to the content restriction."
              }
            ]
          },
          "docs": "This PUT operation adds a specified group to content restrictions for a particular operation on a Confluence page or blog post. The endpoint requires three path parameters: the content ID, an operation key (such as 'read' or 'update'), and the group ID to be added to the restriction. When executed, it grants the specified group permission to perform the designated operation on the content, effectively managing fine-grained access control at the group level. This is useful for administrators who "
        },
        {
          "info": {
            "name": "Atlassian Add User to Content Restriction",
            "type": "http"
          },
          "http": {
            "method": "PUT",
            "url": "https://api.atlassian.com/wiki/rest/api/content/:id/restriction/byOperation/:operationKey/user",
            "params": [
              {
                "name": "id",
                "value": "",
                "type": "path",
                "description": "The ID of the content that the restriction applies to."
              },
              {
                "name": "operationKey",
                "value": "",
                "type": "path",
                "description": "The operation that the restriction applies to."
              },
              {
                "name": "key",
                "value": "",
                "type": "query",
                "description": "This parameter is no longer available and will be removed from the documentation soon.\nUse `accountId` instead.\nSee the [deprecation notice](/cloud/confluence/deprecation-notice-user-privacy-api-migration-guide/) for details."
              },
              {
                "name": "username",
                "value": "",
                "type": "query",
                "description": "This parameter is no longer available and will be removed from the documentation soon.\nUse `accountId` instead.\nSee the [deprecation notice](/cloud/confluence/deprecation-notice-user-privacy-api-migration-guide/) for details."
              },
              {
                "name": "accountId",
                "value": "",
                "type": "query",
                "description": "The account ID of the user. The accountId uniquely identifies the user across all Atlassian products.\nFor example, `384093:32b4d9w0-f6a5-3535-11a3-9c8c88d10192`."
              }
            ]
          },
          "docs": "Updates content restrictions by adding a user to a specific operation-based restriction on a Confluence content item. This endpoint allows administrators to grant a particular user permission to perform a specified operation (such as 'read' or 'update') on restricted content by adding them to the allowlist for that operation. The request requires the content ID, the operation key (the type of restriction being modified), and the user details to be added. This is useful for managing granular acce"
        }
      ]
    }
  ],
  "bundled": true
}