REST API Create Alert : No Owner despite user field filled

Question

Hi,

I'm testing the Create Alert api : POST https://api.opsgenie.com/v2/alerts
Managed to create an alert but fail to provide a Request Owner.

User exists and is visible in the List User API, not blocked, verified.

Tried with id, fullname, username in the json body, to no avail.

How can I change the Request Owner of an alert I create via Create Alert API ?

Nick Haller · Answer

Hi @Romain Bonnot ,

It's not possible to assign an Owner at alert creation. Adding a user as a responder to alert via Create API will simply notify that user of the alert (/add them as a responder) - but the user still needs to acknowledge the alert to take Ownership:

Romain Bonnot · Answer

Hi @Nick Haller ,

Thanks for your detailed answer !

It is indeed my actual process to use the Assign API but it forces me to await API result (well create alert requests are processed asynchronously so it wont really hurt performances) and make a secondary API call to Assign upon every alert creations.

Problem is, I want to create already assigned alerts and from the documentation the user field seams to be exactly what I need.

Can you confirm this field is ignored by the Create Alert API and there is no way to give ownership upon Create Alert call ?

Nick Haller · Answer

Hi @Romain Bonnot ,

It's important to note that Ownership is only given to a user when the alert is assigned to the user, or if a user ack's the alert.

This can be done through our API with either the Assign Alert API, and somewhat through Acknowledge alert API - but realistically the user will want to ack the alert manually so users have better visibility. For example:

Assign Alert API:

Acknowledge Alert API:

^ When an alert is ack'd through the Alert API, alert shows the Alert API as the Owner.

Acknowledging an alert manually:

^ Alert shows the user as the Owner.