Update Ticket API
The Update Ticket API section allows users to modify existing ticket information sourced from external systems. Through this API, users can seamlessly update ticket details accordingly.
UpdateTicket.
POST
https://<sub domain>.kapturecrm.com/update-ticket-from-other-source.html/v.2.0
Authentication:
To access this API endpoint, you need to include your API key in the request headers. For authentication, use the following header:
Request Body
The request body should be a JSON object containing the details of the ticket to be updated. Here are the list of parameters.
Name | Mandatory | Type | Description |
---|---|---|---|
ticket_id | Yes | string | Ticket id to be updated |
sub_status | Yes | string | The key of sub status should be passed for example:- Pending - P Closed - CL |
queue | No | string | The key of the queue name needs to be passed |
Please map in the request body if there's any extra associate body according to your use case.
Response Body
The API responds with a JSON object containing the details of the updated ticket. If successful, the response will include the ticket ID and the other updated relevant information.
Response | Response Messages |
---|---|
{ ..., "status": "success"} | Ticket updated successfully. |
{"message": "Invalid Auth Key","status": "failed"} | Authorization key is either not passed in header, or incorrect, or expired/disabled |
{ "message": "No Data found/ticket_id is missing", "status": "failed" } | ticket_id field is either missing or empty in request body. |
{ "message": "Invalid Format.callback_date should be yyyy-MM-dd hh:mm:ss.", "status": "failed" } | Invalid Format. |
Error Codes
Error Codes | Description |
---|---|
400 | Bad Request - Invalid parameters or missing data |
401 | Unauthorized - Invalid or missing API key |
403 | Forbidden - Insufficient permissions |
404 | Not Found - Resource or endpoint not found |
500 | Internal Server Error - Server-side issue |
Example of a working curl
Last updated