Can I use Integration Service to create a webhook receiver?

[ChiragManh]

It would be great if Integration Services can be used to create an API itself.

Here is the usecase:

1. Receive a webhook call with payload.
2. Validate payload
3. Delivery Payload into PubSub

What I noticed is that API trigger is just to launch Integration; but not to actually receive a payload.

[ChiragManh]

It appears that Using VAR, I can create a variable that will be an input to the API. But if I need to receive a JSON payload  is there a way to do it? A sending app would just make a text/json request  - not really feed it into a specific field.

[shaaland · Accepted solution]

Hi @ChiragManh , 

This use case can be done, but may require an API gateway in front of Integration. The Integration Execute API was created to be very generic, so that you can pass in multiple variables of different types [an array of inputs], and produce multiple responses of different types [an array of outputs], which allows you to cover any use case of inputs or outputs.

For something like a Webhook that you don't have control over, we do have plans to support the most common Webhook patterns that modern SaaS apps use, but until that is a feature in the product, the way to do this today would be to put Apigee API Management Gateway as the receiver of the Webhook, and then it could formulate the payload for the Integration Execution API and then call the Integration API.  You could theoretically use any other API gateway as well, but we have only tested with Apigee so far.  

Thanks for your question!   

Scott

[ChiragManh]

Thanks @sh.

Yes - using API Gateway would be a proper solution for those using API gateway already. For one off use case, having a mechanism such as Integration would be useful.