Back to Integrations Guides

Outgoing Webhooks vs. Generic Webhooks

Introduction

AAArdvark has two kinds of webhooks, and it’s easy to mix them up. The quickest way to keep them straight is to think about which direction the data flows.

At a glance

Outgoing webhookGeneric webhook
DirectionAAArdvark → your serviceYour service → AAArdvark
What triggers itSomething happens in AAArdvark (a new issue, a finished scan…)Your system sends us a request
What you set upA URL on your side, plus the events you wantA URL on our side that accepts your requests
Good forPushing AAArdvark events into your own toolsLetting your tools kick off actions in AAArdvark

Which one do I need?

If you want AAArdvark to notify your tools when something happens – a new issue is found, a scan finishes, a status changes – that’s an outgoing webhook. AAArdvark does the pushing.

If you want your tools to trigger something in AAArdvark – like kicking off a scan from a CI pipeline or a CMS deploy hook – that’s a generic webhook. Your system does the pushing.

In short, outgoing webhooks are for listening, generic webhooks are for triggering.

Still stuck?

File a support ticket with our five-star support team to get more help.

File a ticket

  • This field is for validation purposes and should be left unchanged.
  • Please provide any information that will be helpful in helping you get your issue fixed. What have you tried already? What results did you expect? What did you get instead?

Related Guides