We already have a specific guide for Asset Events, but even that does not enlist all the steps. We'll make sure to update the guide accordingly. Thanks for your feedback!

I think your event registration is still against the Service Account (JWT) client-id. Could you try creating an event-registration against the oAuth client-id and then trigger some events?

The person with which you consented should be the same person who is triggering the events / performing actions on Creative Cloud. Debug Tracing will show you the events getting delivered.

This generally comes when your client-id does not have the creative_sdk scope and you request for it in the consent URL. Have you added any APIs in your project? Could you try this trick and check again?

You can try with a generic redirect URL for now, say https://adobe.com, and give your application (client-id) the consent (see screenshot below). This should be enough for us to forward the events to your application on your behalf.

I think I understand what your problem is. Are you trying the consent request with a Service Account (JWT) client-id? If yes, then can you try once with an oAuth based client-id.

Yes, you can only share projects with people who are added to your respective organization, but I don't think we need to take that route as I may have a better solution to help debug this further. For that, I will require your event (webhook) registration-id which you can get by following the below ...

The screenshot doesn't provide much help in debugging this further. What if you can share a document that only I can view (my adobe email id is stanwar@adobe.com)? Also, one of my speculation would be that this client-id is not enabled for all types of accounts. How are you logging in after you ente...

No the request works from a browser, so it does expect a HTTP GET. I am not sure how a PM is possible here. Could you instead create a dummy project mimicking the current project, and share the request for that instead? We can then delete the dummy project.   

Interesting. I am not sure why that is happening then. Can you share the request you are trying to execute? Also, have you tried once with the browser (maybe Postman is not able to understand the redirects).