{
  "opencollection": "1.0.0",
  "info": {
    "name": "Atlassian Admin Account State API",
    "version": "1.0.0"
  },
  "request": {
    "auth": {
      "type": "bearer",
      "token": "{{bearerToken}}"
    }
  },
  "items": [
    {
      "info": {
        "name": "State",
        "type": "folder"
      },
      "items": [
        {
          "info": {
            "name": "Atlassian Modify the State of an Issue",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.atlassian.com/repositories/:workspace/:repo_slug/issues/:issue_id/changes",
            "params": [
              {
                "name": "issue_id",
                "value": "",
                "type": "path",
                "description": "The issue id"
              },
              {
                "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"
              }
            ],
            "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 POST operation allows you to modify the state of a specific issue within a Bitbucket repository by submitting change requests to the issue's change log. The endpoint requires three path parameters: the workspace identifier, the repository slug, and the issue ID you want to update. When called, it creates a new change entry that can update various issue properties such as status, priority, assignee, or other configurable fields depending on your repository's issue tracker settings. This oper"
        },
        {
          "info": {
            "name": "Atlassian Retrieve the Inheritance State for Repository Settings",
            "type": "http"
          },
          "http": {
            "method": "GET",
            "url": "https://api.atlassian.com/repositories/:workspace/:repo_slug/override-settings",
            "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 retrieves the inheritance state configuration for settings within a specific Bitbucket repository. By making a GET request to the endpoint with the workspace identifier and repository slug, you can determine which repository settings are being inherited from the project level versus those that have been explicitly overridden at the repository level. This is particularly useful for administrators who need to understand the configuration hierarchy and manage settings inheritance"
        },
        {
          "info": {
            "name": "Atlassian Set the Inheritance State for Repository Settings",
            "type": "http"
          },
          "http": {
            "method": "PUT",
            "url": "https://api.atlassian.com/repositories/:workspace/:repo_slug/override-settings",
            "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 administrators to configure the inheritance behavior of settings for a specific Bitbucket repository within a workspace. By making a PUT request to this endpoint, users can control whether repository settings should inherit values from the project or workspace level, or use custom overrides specific to that repository. This is particularly useful in organizations that want to enforce certain settings across multiple repositories while allowing selective customization fo"
        },
        {
          "info": {
            "name": "Atlassian Get Content State",
            "type": "http"
          },
          "http": {
            "method": "GET",
            "url": "https://api.atlassian.com/wiki/rest/api/content/:id/state",
            "params": [
              {
                "name": "id",
                "value": "",
                "type": "path",
                "description": "The id of the content whose content state is of interest."
              },
              {
                "name": "status",
                "value": "",
                "type": "query",
                "description": "Set status to one of [current,draft,archived]. Default value is current."
              }
            ]
          },
          "docs": "This API operation retrieves the current state of a specific Confluence content item by its unique identifier. When called, it returns information about the content's workflow state, including details such as the state name, color coding, and any associated metadata that indicates where the content sits within its defined lifecycle or approval process. This is particularly useful for tracking content through editorial workflows, publication processes, or custom state management systems configure"
        },
        {
          "info": {
            "name": "Atlassian Set the Content State of Content and Publishes New Version of the Content",
            "type": "http"
          },
          "http": {
            "method": "PUT",
            "url": "https://api.atlassian.com/wiki/rest/api/content/:id/state",
            "params": [
              {
                "name": "id",
                "value": "",
                "type": "path",
                "description": "The Id of the content whose content state is to be set."
              },
              {
                "name": "status",
                "value": "",
                "type": "query",
                "description": "Status of content onto which state will be placed. If draft, then draft state will change.\nIf current, state will be placed onto a new version of the content with same body as previous version."
              }
            ],
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "This API operation allows you to set or update the content state of a specific Confluence page or blog post by its ID, which triggers the creation and publication of a new version of that content. When invoked via a PUT request to the endpoint, it accepts the content ID as a path parameter and the desired state information in the request body, then applies that state to the content item while automatically incrementing its version number. This is particularly useful for implementing workflow sta"
        },
        {
          "info": {
            "name": "Atlassian Removes the Content State of Content and Publishes New Version",
            "type": "http"
          },
          "http": {
            "method": "DELETE",
            "url": "https://api.atlassian.com/wiki/rest/api/content/:id/state",
            "params": [
              {
                "name": "id",
                "value": "",
                "type": "path",
                "description": "The Id of the content whose content state is to be set."
              },
              {
                "name": "status",
                "value": "",
                "type": "query",
                "description": "status of content state from which to delete state. Can be draft or archived"
              }
            ]
          },
          "docs": "This API operation removes the current content state from a specified Confluence page or blog post and automatically publishes a new version of that content. By sending a DELETE request to the endpoint with the content ID, the system clears any workflow or review state that was previously applied to the content item, essentially resetting it to a stateless condition. This action is irreversible and creates a new version in the content's history, allowing teams to track when state information was"
        }
      ]
    }
  ],
  "bundled": true
}