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 calls can be used to interact with third party software which supports REST API calls, including an almost unlimited number of Open REST APIs or automatization of form submits to a website.
This section covers the HTTP Get Request, but these HTTP components are available:
An overview/example for use is found in the section, Call external HTTP(s) rest apis
Common for all components
All components can convert a returned JSON document to XML for futher processing in NG2. The returned documents are added as the payload in the workflow and the following workflow variable is set: interformng.httpReturnCode=### where ### is the HTTP return code (200=OK, 403=Access denied etc)
Prerequisites
Basic knowledge on how the HTTP protocol works.
The HTTP Get Request is a Advanced, utilities workflow component with these parameters:
The parameters are described here:
Field | Type | Description |
|---|---|---|
URL | URL | The URL to call |
Output type | Dropdown | The expected receive type from the remote REST API. If the service returns JSON and “Convert JSON to XML” is checked, then the output type should be set to XML. |
HTTP method | Dropdown | The method to use for sending this. |
Convert JSON to XML | Checkbox | If checked, then the returned document from the REST API must be JSON and it will be converted to XML |
Header Name* | String | HTTP Header, name of the header. Linked with value. |
Header Value* | String | HTTP Header value. The content of the header, linked with name |
Parameter Name* | String | A parameter name for this request, linked with value. |
Parameter Value* | String | A value for a parameter, linked with name |
Related Articles
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 ...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 ...HTTP Post multipart 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 ...HTTP Post body only 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 ...Infor System-Link request
The workflow component, Infor System-Link request is a prerequisite for other Infor System-Link components like the Create attachment with Infor System-Link component. The Infor System-Link request component has this parameter: In order to the ...