Linking Label to the Ticket

NOTE: User must be logged in as admin to access this API URL : v3/labels-ticket Method: POST Query Parameters : Parameter Type Possible Values Required/Optional Description ticket_id Integer Required ID of the Ticket Labels Array Required Label Name RESPONSE: {     “success”: true,     “message”: “Labels updated successfully” }

Read More

Linking Tag to the Ticket

NOTE: User must be logged in as admin to access this API URL : v3/add-tag Method: POST Query Parameters : Parameter Type Possible Values Required/Optional Description ticket_id Integer Required ID of the Ticket tags Array Required Tag Name RESPONSE: {     “success”: true,     “message”: “Tags updated successfully” }

Read More

Change ticket department

URL : v3/api/ticket/change-department Method : POST Query Parameters : Parameter Type Optional/Required Description ticket-id integer Required Ticket id of current ticket dept-id integer Required Id of new department Response : { “success”:true, “Message”:”Ticket department changed successfully” }  

Read More

Change ticket due-date

URL : v3/api/ticket/change-duedate Method : POST Query Parameters : Parameter Type Optional/Required Description ticket-id integer Required Ticket id of current ticket duedate string Required The new due date. Due date must be sent as string in y-m-d hh:mm:ss format in agent’s timezone Response : { “success”:true, “Message”:”Ticket duedate changed successfully” }  

Read More

Get form data

URL : v3/api/get-form-data Method : GET Query Parameters : Parameter Type Possible values Optional/Required Description category string ticket, user, organisation, asset, change Required It is the category of the form which  has to be fetched Response : {   “success”:true,   “data”:{ “form_fields”:[         {            “id”:1, “title”:”title”,            “pattern”:””,//any regex pattern “sort_order”:1,            “type”:”email”,            “required_for_agent”:1,            “required_for_user”:1,            “display_for_agent”:1,            “display_for_user”:1,            “default”:1,            “media_option”:”0″, […]

Read More

Post form data (will only be used by admin panel)

URL : v3/api/post-form-data Method : POST Query Parameters : None Body Parameters : Parameter Type Possible values Optional/Required Description category string ticket, user, organisation Required It is the category of the form which  has to be fetched form-fields array Array of objects Required Form fields which are updated or newly created. Please read below for […]

Read More

Delete form data (will only be used by admin panel)

URL : v3/api/delete-form-data Method : DELETE Query Parameters : Parameter Type Optional/Required Description id integer Required Id of the field that is required to be deleted type string Required Whether field or option Possible values are “option” ,”label” and “field” Response : { “success”:true, “Message”:”Successfully deleted” }  

Read More

Add Collaborators

URL : v3/api/ticket/collaborators Method : POST Query Parameters : Parameter Type Optional/Required Description ticket-id integer Required Ticket id of current ticket collaborator-ids Array Required Array of collaborator ids Response : { “success”:true, “message”:”Successfully added” }  

Read More

Create User and add him/her as Collaborator

URL : v3/api/ticket/create-add-collaborator Method : POST Query Parameters : Parameter Type Optional/Required Description ticket-id integer Required Ticket id of current ticket name string Required Name of the collaborator email string Required Email of the collaborator Response : { “success”:true, “message”:”Successfully added” }  

Read More