You can now call out from your App Connect flow to any HTTP endpoint.

To use the HTTP connector, select its action, ‘Invoke method’, from the applications panel. You can do this in both event-driven and API flows.

To call the endpoint you’ll need to specify its URL and the HTTP method to invoke it with. App Connect currently supports GET, POST, PUT, PATCH, DELETE, and HEAD as methods. You can also optionally include request headers in JSON format as key-value pairs (as shown in the image below), and a request body, whose format is determined by the endpoint you’re calling.

All the input fields, as well as the response headers and response body that the endpoint returns, are available for use later in your flow.

This now enables you to integrate with APIs in your organization, as well as third party APIs.

5 comments on"Introducing the App Connect HTTP connector"

  1. What is the endpoint is secured by Kerberos or is none JSON like Thrift

    • Hi Mike,
      At present, we do not support calling Kerberos-secured endpoints or Thrift endpoints with the HTTP connector. Could you give us more details of your requirement here so we could work with this and consider this as a future enhancement? Thanks

      • Sure, we have in house a bunch of JAX-RS (CRUD) Services which are Secured via Kerberos, that will send out a www-negotiate handshake.
        The Objects are java pojo generated from a Thrift schema, and we use Thrift Binary protocal for serialization
        application/vnd.apache.thrift.binary.

Join The Discussion

Your email address will not be published. Required fields are marked *