comparing API trigger to REST

[govardhandatla]

Hi team,

I am am trying to compare API trigger to a REST.
Just wanted to know if we are able to pass request method, query params, headers etc.. compared to a REST call.
Is an API trigger always default to POST and all the input variables part of request body?

[hartmann · Accepted solution]

Hello,

At this current point in time the API trigger supports a POST method to execute a specific integration execution (more on this here: https://cloud.google.com/application-integration/docs/configure-api-trigger). This "API Trigger" use case typically involves some sort of fulfillment/processing layer to receive data to/from an upstream system, hence the POST method was preferred.

If you would like to support more robust API Management capabilities, I would recommend looking into Apigee's API Management platform, which seamlessly connects into an application integration process.

Thanks!

[hartmann · Accepted solution]

Hello,

At this current point in time the API trigger supports a POST method to execute a specific integration execution (more on this here: https://cloud.google.com/application-integration/docs/configure-api-trigger). This "API Trigger" use case typically involves some sort of fulfillment/processing layer to receive data to/from an upstream system, hence the POST method was preferred.

If you would like to support more robust API Management capabilities, I would recommend looking into Apigee's API Management platform, which seamlessly connects into an application integration process.

Thanks!

[greb · Accepted solution]

Hi @govardhandatla 

I appreciate your question and thank you for sharing your perspectives. 

I can say that @hartmann  pointed out a great response, the API Trigger in Google Cloud Application Integration presently only supports the POST method. This is due to its purpose of executing integration workflows, where sending structured data in the request body suffices for most scenarios.

However, if your needs involve transmitting query parameters, custom headers, or accommodating other HTTP methods such as GET or PUT, there are a few alternative solutions by using Cloud Functions or Cloud Run as an intermediary layer:

1. Set Up a Middleware Service:
• Deploy a Cloud Function or a Cloud Run instance to act as a flexible HTTP endpoint.
• This service can handle multiple HTTP methods, query parameters, or headers, and preprocess the request.
2. Forward the Processed Request to API Trigger:
• After preprocessing the input (e.g., converting query parameters or headers into a request body), the middleware can make a POST request to the API Trigger endpoint, passing the structured data.

This approach allows you to leverage the API Trigger for workflow execution while extending its capabilities to simulate a RESTful API behavior.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

[govardhandatla]

Thanks @hartmann and @greb for detailed explanation. It was helpful.