Why Server Webhook payload are different from Cloud

[rama prasad sadanakari]

Hi 

We got the bitbucket server and created webhook on repository push it is sending the header and payload

X-Event-Key: repo:refs_changed

But bit bucket cloud repository push is sending the different header and payload:

X-Event-Key: repo:push

repo:push is supported by spring cloud monitor api.

Is is possible bitbucket server can send repo:push event same as cloud webhook.

Could you please let us know why is this difference.

https://confluence.atlassian.com/bitbucket/event-payloads-740262817.html

https://confluence.atlassian.com/bitbucketserver/event-payload-938025882.html

[Sathya Narayanan]

Hi,

Any update on this request will be of great help

[Sathya Narayanan]

Hi,

Even I am trying to integrate bitbucket server with AWS code services using the webhook.

Since the responds type is different I am having a hard time in do it. Please change it or make cloud and server to send the same kind of response so that we can have some leverage on coding.

If you actually have some work around for this webhook reponse problem please let me know and its urgent.

[Mark Ellis]

Hi Rama,

While Bitbucket Cloud and Bitbucket Server share a lot of commonality, some of the internals will actually differ, as is the case here.

I think at this stage it's unlikely we'd change this, but will reconsider if it comes up more often in future.

[IT development Department]

Where can I vote for this change?

We too would very much like these two "events" AND payloads to be alike!