HumDay

Convert a Swagger 2.0 definition passed in the body to OpenAPI 3.0.x in Mermade Swagger2OpenAPI Converter

A documented Mermade Swagger2OpenAPI Converter operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.

Automate this

What this operation does

Convert a Swagger 2.0 definition passed in the body to OpenAPI 3.0.x

  • POSTChanges data · conversionmermade.org.uk/convert

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 Mermade Swagger2OpenAPI Converter 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 Mermade Swagger2OpenAPI Converter operations

All 6 Mermade Swagger2OpenAPI Converter operations

Questions

Can HumDay convert a swagger 2.0 definition passed in the body to openapi 3.0.x in Mermade Swagger2OpenAPI Converter?
Yes. This operation is published in Mermade Swagger2OpenAPI Converter'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 Mermade Swagger2OpenAPI Converter data?
Yes — this is a POST operation, so it changes something in Mermade Swagger2OpenAPI Converter. 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 Mermade Swagger2OpenAPI Converter account.

Where this came from

Read from a published API description for Mermade Swagger2OpenAPI Converter at raw.githubusercontent.com/Mermade/openapi-webconverter/master/contract/openapi.json. The description above is the provider’s own wording, not ours. Last published 2021-06-21.