Integrate AWX wehook notifications to OPSgenie via API Integration

[Perumal_ Gnanapalaniselvi _external_]

Hi,

Note:- AWX is running inside GKE cluster.

I am trying to integrate AWX webhook notifications to OpsGenie, to create alerts whenever jobs getting failed in AWX. I have created API integration for AWX application in the OPSgenie portal and used the same API key for authorization in the AWX webhook notification templates.

Authorization: Genie Key <api_key>

I am getting below error message

textPayload: "2026-01-29 11:18:20,454 ERROR [7a32fffaccf14d98bc4aa1646805ba2d] awx.main.notifications.webhook_backend Error sending webhook notification: 403"

textPayload: "2026-01-29 11:18:20,455 ERROR [7a32fffaccf14d98bc4aa1646805ba2d] awx.main.tasks.system Send Notification Failed Error sending webhook notification: 403"

File "/var/lib/awx/venv/awx/lib64/python3.11/site-packages/awx/main/tasks/system.py", line 350, in send_notifications sent = notification.notification_template.send(notification.subject, notification.body)"

[Aditya Bodke]

Hi,

Thank you for reaching out, Atlassian Community

A 403 from Opsgenie means the request is reaching Opsgenie, but being rejected at the auth layer. In this setup, there are two common issues:

1. Mismatch between integration type and URL

   1. If you created an API integration in Opsgenie, AWX should call:

      • https://api.opsgenie.com/v2/alerts

      • with header: Authorisation: GenieKey <API_KEY>

   2. If you created a Webhook-style integration (Opsgenie gives you a long, unique URL), then:

      • Use that exact URL in AWX

      • Do not add a custom Authorization header — the URL itself handles auth.

If AWX is calling a webhook URL but also sending Authorization: Genie Key <api_key>, Opsgenie will likely respond with 403.

1. Invalid / disabled API key

   1. In Opsgenie, open the integration, make sure it’s enabled, and copy the key again.

   2. Test from a terminal (from your AWX pod if possible):

      curl -X POST "https://api.opsgenie.com/v2/alerts" \ -H "Content-Type: application/json" \ -H "Authorization: GenieKey <YOUR_API_KEY>" \ -d '{"message": "AWX test alert"}'

   3. If this returns 403, the issue is with the key or integration configuration in Opsgenie.

Regards,
Aditya

[Selvi Perumal]

Hi Aditya,

Thanks for your information. 

I have created API integration for AWX, and configured exactly as you mentioned while creating AWX webhook notification templates. But now I am getting 

OPSgenie notification

• Error sending webhook notification: 422 unprocessable entity error

When I checked it from the terminal using CURL, I can successfully create an alert. Only facing issue with AWX.

My observation:- It seems that AWX internally wraps some extra parameters for custom message such as ''subject" and "body" while sending notification, opsgenie doesn't validate this parameter as an expected one. We have to make changes to python code that handles this logic in the AWX.

Any idea??