Best answer

Webhook GET vs. Stripe Integration

  • 1 February 2022
  • 7 replies
  • 193 views

Userlevel 3
Badge +3

Anyone know what the difference is between the Webhook action's GET event vs Custom Request event using the GET method?

In particular, why would the two behave differently with the Stripe API?

Using the Custom Request action event I am able to successfully process a GET method request to the Stripe API.

Using the GET action event with the same URL and Secret Key, however, I get the following error msg:

"The app returned: https://stripe.com/docs/error-codes#parameter-unknown"

"The request contains one or more unexpected parameters. Remove these and try again."

What is the difference in parameters with the GET action and Custom Request GET method?

I am not using any query parameters, nor any arguments in the zap other than the URL and key, i.e. the same parameters in the Custom Request w/a Get method 🤷🏻‍♂️

The URL is Stripe's API, I'm using HTTPS, and the command works fine using cURL with the same secret key (either by the -u flag, or -H "Authorization: Bearer {secret_key}")

curl https://api.stripe.com/v1/customers/cus_uniqueCustomerID \

  -H "Authorization: Bearer sk_live_authToken"


curl https://api.stripe.com/v1/customers/cus_uniqueCustomerID \

  -u sk_live_authToken:

Thanks!

icon

Best answer by Troy Tessalone 1 February 2022, 21:08

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

7 replies

Userlevel 7
Badge +14

Hi @mixelpix 

Are you able to post screenshots with how each Zap step is configured for your GET vs CUSTOM REQUEST?

If you have it working for CUSTOM, then what is your need to solve it for GET?

Userlevel 3
Badge +3

If you have it working for CUSTOM, then what is your need to solve it for GET?

Understanding the difference between the Webhook action's GET event vs Custom Request event using the GET method.

Userlevel 7
Badge +14

@mixelpix 

Are you able to post screenshots with how each Zap step is configured for your GET vs CUSTOM REQUEST?

Userlevel 7
Badge +14

@mixelpix 

For the GET there is this note in the Query String Params section that is likely the root cause of your issue.

 

Userlevel 3
Badge +3

Are you able to post screenshots with how each Zap step is configured for your GET vs CUSTOM REQUEST?

Per the OP, the settings are identical.  I’ve also tried changing the options re: flattening & JSON.

Userlevel 3
Badge +3

 

Userlevel 3
Badge +3

adding the header content-type: application/json makes no difference.