Introducing Product Webhooks!

Webhooks are a simple and flexible way to send data from your Particle devices to other apps and services around the Internet. Particle developers have been able to leverage the power of webhooks for some time, but this feature has not yet been made available to those building products at scale on the Particle platform.

Today, we’re proud to announce that product webhooks are now available as a public beta.

If you a Particle product creator, you have likely come across the challenge of sending data from your fleet of devices to third-party services. Webhooks for products is a tremendous step forward towards simplifying your data pipeline at scale, and is part of a larger effort to provide tight Integrations with services around the Internet.

###How it works

Product webhooks will allow you to define a single webhook than any of the devices in the product’s fleet can trigger.

As devices in your product’s fleet will be running the same firmware, product webhooks are a scalable way to integrate with third-party web services. Trigger a product webhook when you’d like to do thing like:

  • Send a text message, or trigger a payment based on something happening in the real world
  • Pipe information about how a customer’s device is behaving into an analytics service
  • Make an API call to your servers to send personalized content to a device
  • Save data to a hosted database in the cloud

How to get started

If you haven’t already, you’ll want to create and organization and define a product.

Next, check out our documentation which has in-depth information on creating and managing product webhooks. If you get stuck, let us know!

Known Limitations

If you have been using webhooks as a developer, you may be used to seeing webhook events (hook-sent and hook-response) coming through your event stream and visible on your logs hub on the dashboard. For product webhooks, you will not see webhook events coming through the product event stream. You can, however, still see these events on the event stream of the device owner (i.e. if I own a product device as a Particle customer, and my device triggers a product webhook, it will appear in my customer’s event stream).

We realize that you as a product creator will want more visibility into the health of your webhooks, and are working on a solution to provide detailed audit logs of webhooks.

What’s Next

This is a beta release of product webhooks, which means that things will likely be changing & evolving over the next few months. Our current planned improvements for product webhooks include:

  • An audit log for webhooks to gain insight into webhook activity and potential errors
  • Polished firmware macros for subscribing to a product-level webhook

We’re excited for our community to get started, and look forward to the feedback you provide!


This is awesome @jeiden!!

What are the limits for Product Webhooks? Is the current per user quota applied to per customer on the product account?


@sazp96 great question. I’ll say this first – the pricing structure for the Particle platform is likely to change in the next quarter, and include product-level integrations as part of this change. That is one of the reasons why this is being called a beta, as pricing for this feature is likely to be updated soon.

For now, you are able to create up-to 5 webhooks per product. However, stay tuned about pricing announcements in the near future.

1 Like

As a product creator that is venturing making my own products for the first time, the pricing scheme for organizations is intimidating…

I would like to see a price tier made for us… Enthusiasts that want to migrate to a real product but are not ready for a full commitment… Let’s say a pricing structure for us that want to get say 20-50 devices in the wild to touch waters, and then go big. Something to allow us to continue development and testing in a real deployed world scenario.

I know that as developer we have a ton of options but it is not enough to get a real product ready for the real world since the workflows change a little.

I hope you can take this into consideration, something in the range of 100ish a year would be great. I don’t mind a limit in features like say maximum 1 team member, maximum 1 product with maximum say 50 devices in the wild. And probably I could be comfortable with some minor quota limits.

But please make it accessible for us that are looking for the strength to make the leap!


Thanks so much for speaking up @frlobo! That detailed feedback about your needs is extremely helpful. As Jeff mentioned, we’re still working on the pricing model, trying to get it right. We definitely have a tier like the one you describe in mind as part of our offering, but our initial announcement of new pricing may not include that tier because of differentiating features that we need to build first.

So thank you, we’ve got your use case in mind, and we can’t wait to build it for you!

1 Like

Thanks a lot for the response!

This is what I love about this community!

Thanks for listening and I can’t wait to see a tier that will give me the strength to move to the next level!

1 Like

This is cool!. How about receiving data like the current weather or polling something?

@Nimonster this is totally possible! We will be adding more examples to our docs soon for use cases like this

1 Like

I finally got around to trying this out. The Product Webhooks work great and allows me to use AWS Lambda functions to handle events. The product web hooks reduce my cost compared to running an EC2 instance monitoring the server sent events for the product.

The one thing I would like to see added is the ability to setup a single webhook for all events.

For anyone trying to integrate this with AWS Lambda, I had to disable the default attributes and use the JSON additional variables to pass the event info. Here’s what I configured and worked for me:

  "id": "{{PARTICLE_DEVICE_ID}}",
  "value": "{{PARTICLE_EVENT_VALUE}}",
  "event": "{{PARTICLE_EVENT_NAME}}"

I cannot edit a webhook once it was created, had to delete it and create a new one. I am using safari on Mac. Any idea please.

That has always been the behavior with webhooks. In order to change one you must delete it and recreate it. You can not edit.