API

It would be nice to be able to query all workflows by build status rather than hitting multiple endpoints, especially if the workflow id is not known (this is our use case -- queuing new workflows if there are workflows in progress with a particular status).

Feature request: Organization-level API token. Use case and workaround:We use Terraform provider to interact with the CircleCI API, and since CircleCI supports personal and project-level API tokens (but not organization-level API tokens), the current workaround involves service user which generates an API token, which is suboptimal. CCI-I-1546

This is similar to GitHub Action's GITHUB_TOKEN. Ideally, this token is auto-rotated by CircleCI so it doesn't go stale. CCI-I-1510

Personal API tokens can access all projects the user has access to, but they also allows the requester to perform API accesses that write.Project tokens are read-only, but they can only access a single project.I need a way to create a single token that only allows read access but can access multiple projects. This could be done with a Personal API token if Personal API tokens could be configured to have read-only scope. CCI-I-1495

Currently the only way of debugging a project via SSH is by using your public keys attached to a VCS such as Github or Bitbucket. I am proposing an idea in which we can add our public keys used for debugging via SSH directly to CircleCI rather than using the public keys listed on Github and Bitbucket. I am aware the demand for this is quite low, however I think for certain individuals it can be greatly beneficial, like myself. So essentially something like this: curl -X POST --header “Content-Type: application/json” -d ‘{“type”:“public-user-key”}’ https://circleci.com/api/v1.1/project/:type/:username/:project/checkout-key?circle-token=:token But obviously type replaced with CircleCI, instead of the conventional type being a VCS such as Github. CCI-I-1104

I want to be able to get the recent builds for an organization I am a part of via the API.I should not have to follow the projects I want the recent builds of. CCI-I-1051

It is currently not possible to view via the API the user who approved a manual approval step. This user should be listed when requesting the data for the job that required approvalhttps: //circleci.com/docs/api/#recent-builds-for-a-single-projectThe API currently lists: "committer_name" : "Allen Rohner", "committer_email" : " arohner@gmail.com ", A similar convention for approval could be used, and to indicate if a job is an approval job. Example: approval: { "approval" : true "approver_name" : "Allen Rohner", "approver_email" : " arohner@gmail.com ", } CCI-I-822

I would like to rotate our circle api token once a month with an automated process. I did not see such an endpoint. It would be useful to integrate this token into our other key rotation workflows. https://circleci.com/docs/2.0/managing-api-tokens/ This also relates to ticket CCI-I-482 CCI-I-628

Example: - approve_release: type: approval requires: - checkout_and_build filters: branches: only: /master/ expiry: 24h Reasoning: Jobs with type: approval require manual confirm/cancel, and as such are a good control method for jobs that don't need to be run every build, or builds that require review before completion (e.g. releases). One use we have for these job types is to build docker images from successful builds on the fly. We don't need docker images for every build, and there are many builds in a day, so the approval jobs pile up. We don't need any builds older than 24hrs, so a suggestion to prevent a build up of on hold jobs (not sure what impact this has on a CircleCI cloud/personal server) is to introduce an expiry token as part of the workflow description. CCI-I-181