Create Incident API returning 404

I am trying to create an incident using the samanage api, and it's returning 404. I can fetch incidents with GET https://api.samanage.com/incidents, so I know my auth token is working. When posting to the same endpoint with the sample body in the documentation, it comes back with 404.

I'm following the documentation here apidoc.samanage.com/

Find more posts tagged with

samanage

API

Accepted answers

SPSDude

Gotcha! (and sorry for my delayed response)

So, what I would do is take that sample and only use the essentials. That's really just to give you an idea.

When I'm first testing a POST, I like to start with just the required fields. For an incident, that would be the Name, Priority and Requester. Then I'll start adding to the payload and testing incrementally so I know where I'm winning and where I'm losing. (I'm also terrible with API, so this is my slow but safe method)

Try something like this:

{
"incident":{
"name":"Incident Name",
"description":"description",
"assignee":{
"email":"john.doe@email.com"
},
"requester":{
"email":"john.doe@email.com"
},
"priority":"High"
}
}

All comments

SPSDude

Howdy @jasonisrael

I'd love to try and help. Can you share your payload here and we'll see what we can find?

jasonisrael

{
  "incident": {
    "name": "Incident Name",
    "site_id": 1,
    "department_id": 1,
    "description": "description",
    "state_id": 1,
    "assignee": {
      "email": "john.doe@email.com"
    },
    "requester": {
      "email": "john.doe@email.com"
    },
    "priority": "High",
    "category": {
      "name": "Facilities"
    },
    "subcategory": {
      "name": "Equipment"
    },
    "due_at": "Jan 01,2025",
    "add_to_tag_list": "tag1, tag2",
    "remove_from_tag_list": "tag3",
    "tag_list": "tag1, tag2",
    "custom_fields_values_attributes": [
      {
        "id": 10,
        "custom_field_id": 1,
        "value": "content"
      },
      {
        "id": 100,
        "custom_field_id": 2,
        "value": "1"
      }
    ],
    "custom_fields_values": {
      "custom_fields_value": [
        {
          "name": "Text custom field",
          "value": "content"
        },
        {
          "name": "User custom field",
          "user_value": {
            "email": "john.doe@email.com"
          }
        }
      ]
    },
    "incidents": [
      {
        "number": 100
      }
    ],
    "problems": [
      {
        "number": 100
      }
    ],
    "changes": [
      {
        "number": 100
      }
    ],
    "solutions": [
      {
        "number": 100
      }
    ],
    "releases": [
      {
        "number": 100
      }
    ],
    "purchase_orders": [
      {
        "number": 100
      }
    ],
    "configuration_items": [
      {
        "name": "Item name"
      }
    ],
    "configuration_item_ids": [
      100
    ],
    "cc": [
      "jane.doe@email.com"
    ]
  }
}

Thank you! This is the payload I'm using, it's the sample one from the docs here apidoc.samanage.com/

jasonisrael

Hi, did you get a chance to look at this issue?

SPSDude

Gotcha! (and sorry for my delayed response)

So, what I would do is take that sample and only use the essentials. That's really just to give you an idea.

Try something like this:

{
"incident":{
"name":"Incident Name",
"description":"description",
"assignee":{
"email":"john.doe@email.com"
},
"requester":{
"email":"john.doe@email.com"
},
"priority":"High"
}
}

jasonisrael

No worries! I was able to get it working by using that payload, with real values for the assignee and requester emails. I was mostly confused about getting 404 back from a POST request, it made me think I was calling the wrong endpoint entirely. I would have expected a malformed request response, not NotFound in this case.

Thanks for the help.