Webhook console list vs cli list

I have a webhook question. I created 3 webhooks from the console and they work fine when my msom publishes. However, I wanted to write some unit tests using 'particle publish' command and found that my webhooks are never called even though I see the published events with 'particle subscribe'.

The console shows that I have 3 webhooks configured. However when I query the webhook list from the command line, I get a different answer

holla@horton[503]: particle webhook list
Found 0 hooks registered

holla@horton[504]: particle whoami
trace@grndwork.com

Notice that I'm logged in as the same user on console and command line.

So I used the command line to create a webhook

holla@horton[501]: particle webhook list
1.) Hook ID 6864132c******** is watching for "sensor-reading"
and sending to: https://**********
created at 2025-07-01T16:56:12.525Z

Now particle publish works correctly, the aws api endpoint is called.

I discovered this a few minutes ago after fighting with this problem yesterday for hours.

What am I doing wrong? Does this have something to do with the event 'coreid' being set to 'api'?

It looks like the console is using a product webhook, which is what is recommended.

When you use the CLI, by default it uses the integrations in the top level of the sandbox, not a product within the sandbox. You've created two webhooks in your test, and it's possible that both could execute for a real device triggering the webhook.

To make the CLI work with a product webhook, add the --product <product_id> command line option.

Uh ha! I was wondering about that. I poked around the console and figured that out. Thank you so much for the quick response!

holla@horton[508]: particle --product ***** webhook list
Unknown argument 'product'

holla@horton[511]: particle version
3.36.1

For some reason webhook list does not work with product webhooks. But you can see how it works for publish using particle publish --help.

this works, thanks again.