How to assign an incident to a group rather than to a person through email when making an API call

Hello!  You can assign a ticket to a group by using the following:

<assignee_id>5224981</assignee_id>

The number in the middle comes from the ID number of the group you wish to assign to.  This can be found by navigating to Setup>Users & Groups>Groups.  Then, click on the group you wish to get the ID number for and in the URL line in your browser it will show the group's ID like this:

https://instancename.samanage.com/groups/1234567

The number at the end is the Group ID you would use.

As an addition to this, you can use the assignee_id field for users. You may need to use the User record's "unique group", which is the first group_id in its group_ids list.

Hi Mitch,

Where did you find that html? Also, when I put the assignee_id of the group in the json payload, it assigns it to someone else. I tried both a string and an int.

Hi karimb, you can easily browse any record as json or XML by adding .json or .xml to the end of its URL in the browser.

Example: https://yourcompany.samanage.com/users/1609255 turns into https://yourcompany.samanage.com/users/1609255.xml

I use it frequently when I'm troubleshooting.

For the issue you're running into with the json payload, it sounds like maybe just the wrong ID is being used. If you want to paste or link a code sample here I'd be happy to take a look! Please make sure to scrub any sensitive data though 

Alright. Thanks for the tip. Here is a code sample of the payload:

  sa_payload = {
    "incident" : {
      "name": itemResponses[0].getResponse(),
      "description":itemResponses[1].getResponse(),
      "assignee":{
        "assignee_id": "id"
      },
      "requester":{
        "email":formResponse.getRespondentEmail()
      },
      "priority":itemResponses[2].getResponse(),
      "category":{
        "name":category
      },
      "subcategory":{
        "name":subcategory
      }
    }
  }

  sa_options = {
    'method':'post',
    'contentType': 'application/json',
    'headers': {'X-Samanage-Authorization':'Bearer ' + SA_token},
    'payload' : JSON.stringify(sa_payload)
  }

Alright. Thanks for the tip. Here is a code sample of the payload:

  sa_payload = {
    "incident" : {
      "name": itemResponses[0].getResponse(),
      "description":itemResponses[1].getResponse(),
      "assignee":{
        "assignee_id": "id"
      },
      "requester":{
        "email":formResponse.getRespondentEmail()
      },
      "priority":itemResponses[2].getResponse(),
      "category":{
        "name":category
      },
      "subcategory":{
        "name":subcategory
      }
    }
  }

  sa_options = {
    'method':'post',
    'contentType': 'application/json',
    'headers': {'X-Samanage-Authorization':'Bearer ' + SA_token},
    'payload' : JSON.stringify(sa_payload)
  }

...

"assignee": {

  "assignee_id": "id"

},

...

should be 

...

"assignee_id": "id",

...

Oh I did not see that in the API documentation. I will try it out and let you know how it goes!

Alright. I got it to assign to the right team. Thank you so much Mitch!

I'm running into this same issue and unable to get it to assign the incident correctly when trying to assign to the id of a group.  What was the resolution on this?  I can assign with an email just fine, but neither "id" nor "assignee_id" seems to work.  I've tried about every variation I can think of.  The comment above advises to add a comma after the id, but that is actually malformatted json as there isn't an attribute that follows with the "assignee" section, so I wasn't sure if there was a different solution you found?

And of course as soon as I post that I realize what Mitch was saying - there isn't an assignee section in this case, you just use assignee_id at the level that you'd normally use the section of assignee.  Which is odd because that's completely different than assigning to an email, in which case you DO nest the email in the assignee section (this is how the API documentation reads, and there is no mention of using this different structure to assign by assignee_id.

So once I took out the entire assignee section, and replaced it with the single assignee_id attribute, then it worked.  Sorry I didn't notice that 30 seconds BEFORE I posted that.  :-)