Delete an API specification in ReadMe in Readme Endpoints

What this operation does

Delete an API specification in ReadMe

• DELETEChanges data · API Specificationdash.readme.io/api-specification/{id}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. 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.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

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

All 28 Readme Endpoints operations

Questions

Can HumDay delete an api specification in readme 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.

Will this change my Readme Endpoints data?

Yes — this is a DELETE operation, so it changes something in Readme Endpoints. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

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.