{
  "opencollection": "1.0.0",
  "info": {
    "name": "Atlassian Admin Account Executions API",
    "version": "1.0.0"
  },
  "request": {
    "auth": {
      "type": "bearer",
      "token": "{{bearerToken}}"
    }
  },
  "items": [
    {
      "info": {
        "name": "Executions",
        "type": "folder"
      },
      "items": [
        {
          "info": {
            "name": "Atlassian List Executions of Schedule",
            "type": "http"
          },
          "http": {
            "method": "GET",
            "url": "https://api.atlassian.com/repositories/:workspace/:repo_slug/pipelines_config/schedules/:schedule_uuid/executions",
            "params": [
              {
                "name": "workspace",
                "value": "",
                "type": "path",
                "description": "This can either be the workspace ID (slug) or the workspace UUID surrounded by curly-braces, for example `{workspace UUID}`."
              },
              {
                "name": "repo_slug",
                "value": "",
                "type": "path",
                "description": "The repository."
              },
              {
                "name": "schedule_uuid",
                "value": "",
                "type": "path",
                "description": "The uuid of the schedule."
              }
            ],
            "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 endpoint retrieves a list of all pipeline executions that have been triggered by a specific schedule in a Bitbucket repository. By providing the workspace identifier, repository slug, and schedule UUID in the path, users can view the historical execution records for that particular scheduled pipeline. This is useful for monitoring and auditing purposes, allowing teams to track when scheduled pipelines have run, verify their execution history, and identify any patterns or issues with aut"
        }
      ]
    }
  ],
  "bundled": true
}