Okay, so I finally figured this out and I'm going to leave behind how I actually resolved this on my own for "the next guy". ;)

Here's the exact curl that I used to create an incident in OpenDuty:

curl --insecure -H "Content-type: application/json" -H "Authorization: token thisismysecret" -X POST -d '{"service_key":"b893c504c51c26c720056ed94ec53049b9b9d0a4","event_type":"trigger","description":"test","incident_key":"1234567","details":"Details here"}' http://192.168.0.92:9080/api/create_event

Now, just to break this down, here's where each bit comes from:

"Authorization: token thisismysecret" comes from the settings file, specifically, I have this set in my openduty.settings_dev file:

SECURITY WARNING: keep the secret key used in production secret!

SECRET_KEY = 'thisismysecret'

The "service_key" comes from first creating a service, and then creating an API key for the service. In this case, I named my service "Nagios" which had a "Service ID" of "84b689a038614539ad37582519de207e" and I then created the API Key by the name of "nagios_api_key" that ended up being "b893c504c51c26c720056ed94ec53049b9b9d0a4".

Hope this helps someone and that I wasn't just being dense. :)

from openduty.

we have to create first the service ? :(

from openduty.

@gabrielfsousa Yes, you have to create the Schedule, Escalation policy, Service and the API Key in order to be able to send via the API.

from openduty.