When a Podio webhook is triggered by its subscribed event, the hook will send a request to an external url with information about that event. Is it possible to customize the information contained in the request?
For example, I am planning to create a webhook that will be triggered when an app field is updated. The default webhook settings will include
body: { item_id: '12345',
item_revision_id: '2',
type: 'item.update',
hook_id: 54321' }
in the request. However, this means that I have to chain this to another GET request back to Podio if I want to get more information about the updated item (these are 'user' items, so I want things like 'first_name', 'last_name', etc.).
When I create a hook via the API (https://developers.podio.com/doc/hooks/create-hook-215056), is there a way that I can customize it so that the entire updated item record is included in the requests when the hook is called? In the Ruby and PHP client examples, there's an attributes parameter - can you set the request data via attributes and, if so, how should that be formatted?
It is not possible to customize Podio webhook request. Each and every Podio webhook has same structure, and if you need more information about item being updated/created you will need to fire another GET request.
Related
I am creating a custom app on the BigCommerce platform. I am wondering if it is possible to send a webhook request going from BigCommerce when an order has been placed. Currently I can only see that it is sending an email notification, but I would like to send a webhook request to a url instead.
For example, so that a post request is sent from BigCommerce to a certain URL everytime an order has been placed.
Use the Webhooks API to create a new webhook that fires on a new order:
https://developer.bigcommerce.com/api-reference/store-management/webhooks/webhooks/createwebhooks
That includes an endpoint you can specify to listen to events - that payload contains the order id of the new order.
More info here: https://developer.bigcommerce.com/api-docs/store-management/webhooks/overview
And all events here:
https://developer.bigcommerce.com/api-docs/store-management/webhooks/events
How can we create field specific Webhook in podio back-end. We tried by specifying app_field and field_id in webhook URL as per the documentation but it doesn't work it's applying to all the fields not in particular field
I want to test Podio Web Hooks (item.update) through RequestBin. I have created WebHook and it shows in my account. When I created i got one request for Verify on RequestBin URL. But in Podio it is showing as Inactive.
Kindly let me know how can I test further.
You have to validate the hook using the code received from the verify call. The hook will become active only after on successful validation.
Refer Podio documentation on how to Validate hook here, Validate Podio hook verification
So the webhook content is pretty bare bones, it just has request parameters for a variable or two in addition to any URL parameters you are passing based on your webhook URI. There is a whole description of what the parameters provided are here: https://developers.podio.com/doc/hookshttps://developers.podio.com/doc/hooks
Basically whatever is catching your webhook will need to be able to connect to the Podio API and fetch the item with the ID passed in the webhook.
I would like to integrate my backend API with several shopify clients by using webhook created by shopify.
I read that webhook is a push notification triggered by shopify. If I give my server endpoint (receiving order/creating a new customer) to my several shopify clients, how will I identify a different notification?
Will there be a unique identifier(per client) in the notification sent by shopify? It's because if I receive an order notification, I need to identify this order notification with one of my clients in my db.
Please advise me about this use case.
Thanks.
Per the Shopify Webhook Documentation, each webhook from Shopify contains a JSON payload and HTTP headers that provide context.
The X-Shopify-Shop-Domain HTTP header includes the domain of the shop, e.g., johns-apparel.myshopify.com. You can use this to identify the shop.
Every Webhook comes to you from Shopify with security information that allows you to determine if the incoming Webhook is even valid and every Webhook also tells you the shop the Webhook is coming from.
So you can use the shop information to figure things out. Straightforward!
I experimenting with Paypal REST API and I was stunned into a problem with webhooks.
I trying use the following tactic to verify event data - ensure that HATEOAS link with rel == "self" like https://api.sandbox.paypal.com/v1/notifications/webhooks-events/WH-6L177801XL962315K-5B870910V53268712 is present, and ensure that this link starts with expected API endpoint (set in web.config) and reloads event data with it, and use it as trusted event data.
But this tactic fails, it results to 404 instead of getting webhook data.
Who else used Paypal REST API webhooks? How you are verify that the event come from trusted event source?
Update
Was able to get more details on messages received. Response body:
Data [{\r\n \"name\": \"INVALID_RESOURCE_ID\",\r\n \"details\": [],\r\n \"message\": \"Resource id is invalid\"\r\n}]
Headers as JSON object: [{\r\n \"PROXY_SERVER_INFO\": [\r\n \"host=slcsbplatformapiserv3002.slc.paypal.com;threadId=370534\"\r\n ],\r\n \"Paypal-Debug-Id\": [\r\n \"e33a2f285d46f\"\r\n ],\r\n \"SERVER_INFO\": [\r\n \"webhooksplatformserv:ppaas_1_2.v1.notifications.webhooks-events.id.GET&CalThreadId=184&TopLevelTxnStartTime=14b4099eb05&Host=slcsbwebhooksplatformserv3002.slc.paypal.com&pid=29135\"\r\n ],\r\n \"Date\": [\r\n \"Sat, 31 Jan 2015 15:26:44 GMT\"\r\n ],\r\n \"Server\": [\r\n \"Apache-Coyote/1.1\"\r\n ]\r\n}]
The hateoas link should return the same payload as the original webhook event. So there seems to be some issue there.
However, if your intention is to validate if the event came from PayPal then the correct way is to validate the signature included in the webhooks header. This link has more details around the security aspects in webhooks.
https://developer.paypal.com/webapps/developer/docs/integration/direct/rest-webhooks-overview/#event-security