Get a checkout key in CircleCI
A documented CircleCI operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get a checkout key.
- GETReads data
circleci.com/project/{username}/{project}/checkout-key/{fingerprint}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which CircleCI operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other CircleCI operations
- Adds your Heroku API key to CircleCIPOST · changes data
- Creates a new environment variablePOST · changes data
- Creates a new checkout keyPOST · changes data
- Triggers a new build, returns a summary of the buildPOST · changes data
- Create an ssh key used to access external systemsPOST · changes data
- Triggers a new build, returns a summary of the buildPOST · changes data
- Retries the build, returns a summary of the new buildPOST · changes data
- Clears the cache for a projectDELETE · changes data
Questions
- Can HumDay get a checkout key in CircleCI?
- Yes. This operation is published in CircleCI's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my CircleCI account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in CircleCI.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your CircleCI account.
Where this came from
Read from a published API description for CircleCI at raw.githubusercontent.com/kamikazechaser/spec-circleci/master/swagger.yml. The description above is the provider’s own wording, not ours. Last published 2021-06-21.