Message: ticket.complete

Back to Index

Completes a ticket

Schema

Body

No fields

Response Type

string

Relevant Rule Hooks

This rule hook runs every time a ticket receives a complete message.

OnTicketComplete

Example: Complete a Ticket

Complete a Ticket

Request

POST https://<hantera-hostname>/resources/actors/ticket/<TICKET ID>
Authorization: Bearer <YOUR TOKEN>
Content-Type: application/json

[{
    "type": "complete"
}]

curl -i -X POST \
  https://<hantera-hostname>/resources/actors/ticket/<TICKET ID> \
  -H 'Authorization: Bearer <YOUR TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '[{
    "type": "complete"
}]'

Invoke-WebRequest `
-Uri "https://<hantera-hostname>/resources/actors/ticket/<TICKET ID>" `
-Method POST `
-Headers @{Authorization="Bearer <YOUR TOKEN>"; 'Content-Type'="application/json"} `
-Body '[{
    "type": "complete"
}]'

Response

HTTP/1.1 200 OK
---

{
  "paths": [
    "resources/actors/ticket/0199aa1f-830e-7123-9b0f-d5c35691e333",
    "resources/actors/ticket/return/RE100013",
    "resources/actors/ticket/return/return2"
  ],
  "data": {
    "complete": "OK"
  }
}

Ensure you use the correct <TICKET ID> so you don’t get a NOT_FOUND error. You can also use the preview mode to test the message before applying it live.

Back to Index