Get changelog in Readme Endpoints
A documented Readme Endpoints 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 changelog
- GETReads data · Changelog
dash.readme.io/changelogs/{slug}
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 Readme Endpoints 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 Readme Endpoints operations
- Create custom pagePOST · changes data
- Create versionPOST · changes data
- Create changelogPOST · changes data
- Upload an API specification to ReadMePOST · changes data
- Delete custom pageDELETE · changes data
- Update custom pagePUT · changes data
- Delete changelogDELETE · changes data
- Update changelogPUT · changes data
Questions
- Can HumDay get changelog in Readme Endpoints?
- Yes. This operation is published in Readme Endpoints'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 Readme Endpoints account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Readme Endpoints.
- 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 Readme Endpoints account.
Where this came from
Read from a published API description for Readme Endpoints at raw.githubusercontent.com/readmeio/oas/master/packages/examples/3.0/json/readme.json. The description above is the provider’s own wording, not ours. Last published 2020-07-22.