# Incoming Webhook verification status 500

**URL:** <https://forum.mattermost.com/t/incoming-webhook-verification-status-500/1047>\
**Category:** Troubleshooting\
**Created:** [March 10, 2016, 7:00pm UTC](https://forum.mattermost.com/t/incoming-webhook-verification-status-500/1047 "2016-03-10T19:00:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mdxdave](https://avatars.discourse-cdn.com/v4/letter/m/e36b37/32.png) [@mdxdave](https://forum.mattermost.com/u/mdxdave)\
**Post date:** [March 10, 2016, 7:00pm UTC](https://forum.mattermost.com/t/incoming-webhook-verification-status-500/1047/1 "2016-03-10T19:00:38Z")

</div>

Crashlytics (or [fabric.io](http://fabric.io)) offers an integration with Slack or custom webhooks.  
Mattermost webhooks are described as compatible to Slack, but unfortunately it seems that not any service with Slack integration is compatible to mattermost.

Fabric uses an **verification** webhook. They send some request to the webhook including following payload:

```json
{"event": "verification", "payload_type": "none"}

```

Using curl:

```ssh
 curl -i -X POST -d 'payload={"event": "verification", "payload_ty": "none"}' https://example.com/hooks/abc

```

Mattermost responses with status code 500:

> HTTP/1.1 500 Internal Server Error  
> […]  
> X-Ratelimit-Limit: 10  
> X-Ratelimit-Remaining: 9  
> X-Ratelimit-Reset: 1  
> X-Request-Id: s64pjxn8gjb35xeghxyd849q4h  
> X-Version-Id: 2.0.0.1456450262

and following response body:

```json
{"id":"web.incoming_webhook.text.app_error","message":"No text specified","detailed_error":"","request_id":"s64pjxn8gjb35xeghxyd849q4h","status_code":500,"is_oauth":false}

```

More infomation: [http://support.crashlytics.com/knowledgebase/articles/102391-how-do-i-configure-a-custom-web-hook](http://support.crashlytics.com/knowledgebase/articles/102391-how-do-i-configure-a-custom-web-hook)

As result Fabric/Crashlytics can not be integrated with Mattermost

I do not known if other services rely on such an verification event to verify the access of an webhook.

---

<div class="post-metadata">

**Author:** ![steve.russell](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@steve.russell](https://forum.mattermost.com/u/steve.russell)\
**Post date:** [March 22, 2016, 5:24pm UTC](https://forum.mattermost.com/t/incoming-webhook-verification-status-500/1047/2 "2016-03-22T17:24:38Z")

</div>

I’m seeing the same thing trying to integrate OpsGenie alerts into Mattermost. Have you had any luck?

---

<div class="post-metadata">

**Author:** ![matterbot](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/matterbot/32/467_2.png) [@matterbot](https://forum.mattermost.com/u/matterbot)\
**Post date:** [March 22, 2016, 7:34pm UTC](https://forum.mattermost.com/t/incoming-webhook-verification-status-500/1047/3 "2016-03-22T19:34:53Z")

</div>

Hi @steve.russell, hi @mdxdave, thanks for the report!

This change seems reasonable to add.

Wondering if anyone in the community would be interested in helping make a pull request to support this?

If someone makes a pull request with the addition we have [a process to spin up a test server for you to try it out](https://github.com/mattermost/platform/pull/2487) and make sure everything is working before the changes get merged.