CircleCI Ideas
Home
API
115
Powered by Canny

API

If you're unsure of which feedback category to select, please reference our guide in the changelog or use the ""uncategorized" bucket so we can get your feedback to the right team.
Add API Endpoints For Job Resource Usage
Being able to programmatically see and compare job resource usage would be helpful. Bonus if there was an endpoint to easily tell if jobs weren't consuming all of their resources, say if they were below 50% usage.
4
·

complete

Trigger build via API using PR number
Back then using v1, users were able to trigger build for PR using PR number. - For example, curl -X POST --header "Content-Type: application/json" -u $CIRCLE_TOKEN -d '{ "branch" : "pull/2"}' https://circleci.com/api/v2/project/<vcs>/<username>/<project>/pipeline It's not anymore available for v2 and this function should be supported for PR builds. CCI-I-1280
7
·

complete

Users should be able to Self Serve Audit Logs
Users should be able to pull and download the audit logs independently. CCI-I-847
10
·

complete

Enable and configure webhooks using API
Now that Webhooks is available, there should be the ability to enable and configure it on a per-project basis using the API and to be able to disable it per project via API also.
3
·

complete

Trigger workflows via CircleCI REST API
Currently REST API can only invoke the build step and does not properly support triggering steps within a workflow, or kicking off a full workflow. We would like the ability to use the REST API to:1. kick off a step within a workflow kick off an entire workflow CCI-I-192
30
·

complete

Public API to get Workflow build Status
Currently we use the public API to get the status of our master builds. However, since we have moved over everything to use Circle 2 and have started using workflows the existing api is insufficient. I know you added an api to launch workflows but how about getting the status of a workflow. Is this something you can add to the API? It would be immensely valuable for us as we run continuous deploy and need to know as soon as possible when a master build fails. CCI-I-569
11
·

complete

Trigger specific workflow with circleci 2.1 API end point
Add the ability to trigger a specific workflow by name with the API, instead of running the full config. CCI-I-821
3
·

complete

Filter by date on Insights API
Add date filters to the insights API to pull data for specific time frames. CCI-I-1521
1
·

complete

Workflow metadata to insights
It appears workflow metadata isn't in insights and isn't really easily retrieved from the api. I just want to be able to track the time of these workflow over time. Knowing if those numbers are going up are going down would be a big quality of life improvement for development. You store the numbers somewhere just let me track them :) Screenshot CCI-I-1217
1
·

complete

Powered by Canny