My Products
Help
zimplydaniel
CONTRIBUTOR **

How to get webhook when a new tenant adds our application?

by zimplydaniel

Hi all!

 

We have published our application in the App Store and have activated a webhook for Visma Connect Idp. The goal is to get a webhook sent every time a new customer adds our application in the Visma App Store.

 

We have setup the webhook and tested it using the "Test webhook" button on Client Application Authorized. We receive a example payload to our webhook, so the setup works fine. However, when we try to add our application using our sandbox company in the App Store, we do not receive a webhook from Visma. The plan is to fetch the tenant_id and save it in our database so that we can add the customer to our application.-

 

What are we doing wrong or does the webhook not work as we expect?

 

We have registered the application to these webhook events:

TENANT_APPLICATION_ADDED

TENANT_APPLICATION_DELETED

TENANT_APPLICATION_FEATURES_CHANGED

TENANT_APPLICATION_RESUMED

TENANT_APPLICATION_SOFT_DELETED

TENANT_APPLICATION_SUSPENDED

TENANT_APPLICATION_USER_ROLES_CHANGED

TENANT_MODIFIED

7 REPLIES 7
zimplydaniel
CONTRIBUTOR **

by zimplydaniel

Anyone who knows this?

Marten Voort
VISMA

by Marten Voort

Hi zimplydaniel, we are investigating this and will come back to you as soon as possible.

zimplydaniel
CONTRIBUTOR **

by zimplydaniel

Great, thanks!

Accepted solution
Marten Voort
VISMA

by Marten Voort

Hi, this should work now, can you verify?

zimplydaniel
CONTRIBUTOR **

by zimplydaniel

Hi Marten,

We have tested it out again, but it is not working. We do get the webhook when deleting the application, but not when adding it again.

Let me know if we can support you in getting this going.

Marten Voort
VISMA

by Marten Voort

Hi Daniel, thx! I just tested this, using an invitation code, deleting and adding both trigger webhooks for me, see screenshot. Have you enabled the Idp scopes?
2024-11-26 16_39_24-Visma App Store.png

zimplydaniel
CONTRIBUTOR **

by zimplydaniel

I checked again, and it works! Did not see it first because of a delay. Thanks for fixing this!