Delete a template in SwaggerHub Registry
A documented SwaggerHub Registry operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Delete a template
- DELETEChanges data · Templates
api.swaggerhub.com/templates/{owner}/{templateId}
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 SwaggerHub Registry operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other SwaggerHub Registry operations
- Add a new commentPOST · changes data
- Add a new commentPOST · changes data
- Create a project in an organizationPOST · changes data
- Create or update an APIPOST · changes data
- Create or update a domainPOST · changes data
- Create a new API versionPOST · changes data
- Create or update a templatePOST · changes data
- Create a new domain versionPOST · changes data
Questions
- Can HumDay delete a template in SwaggerHub Registry?
- Yes. This operation is published in SwaggerHub Registry'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 SwaggerHub Registry data?
- Yes — this is a DELETE operation, so it changes something in SwaggerHub Registry. 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 SwaggerHub Registry account.
Where this came from
Read from a published API description for SwaggerHub Registry at api.swaggerhub.com/apis/swagger-hub/registry-api/1.0.66. The description above is the provider’s own wording, not ours. Last published 2023-02-17.