Swagger HTTP workflow component

Swagger HTTP workflow component

The advanced, utilities workflow component, Swagger HTTP can load a Swagger JSON definition can be loaded and a request from the API can be selected.

 

An HTTP component is then generated with URL, output type, parameter names and header names pre-filled.

Either GET, POST or multipart POST component is selected, based on selected request. For POST components, the method (POST, PUT or PATCH) is also auto-selected.

 

The Swagger HTTP component has this parameter:


  1. URL to Swagger JSON definition
    In this parameter you need to enter the URL of the swagger json definition, that you want to load. After entering it you need to click Load swagger definition and then apply.
    • Related Articles

    • Advanced Utilities workflow components

      The Advanced Utilities workflow components are as follows: Append to zip archive. Appends the payload to a zip file. The zip file will be created, if the referenced zip file does not exist. Attachment to payload. Takes a named attachment, removes it ...
    • HTTP GET Request component

      In InterformNG2 it is possible to call (most) external HTTP REST APIs / Webservices and form submits using workflow components. The calls are based on RFC2616 Hypertext Transfer Protocol HTTP/1.1 https://www.ietf.org/rfc/rfc2616.txt The external HTTP ...
    • HTTP Post request

      In InterformNG2 it is possible to call (most) external HTTP REST APIs / Webservices and form submits using workflow components. The calls are based on RFC2616 Hypertext Transfer Protocol HTTP/1.1 https://www.ietf.org/rfc/rfc2616.txt The external HTTP ...
    • Error workflow component

      The workflows, that you can setup in InterformNG2 can be very long and complex and in some cases e.g. for debugging you might want to force an error in the workflow. Another reason why you might want to force an error, could e.g. be that an input XML ...
    • Retry-repeat workflow component

      The advanced utilities workflow component, Retry-repeat, can help if you have a workflow component that sometimes fails (for example, due to network connection issues). You can use this to retry a subtree of workflow components until no error occurs, ...