Search for tickets with a given phrase. The phrase is identical to the one used in the Tickets application and additionally offers suggestions for ticket fields and values within these fields. The response list of tickets is represented by their ticket IDs which can be used for further requests.

The request is supposed to be send using the POST verb, including a request body consisting of JSON to describe the search request.

The following request fields can be set in the JSON posted to the server. The servers response is either an error or an object with RESPONSE fields from below.

# Request
POST /api/ticket/search HTTP/1.1
Authorization: Bearer VGhpcyBpcyBqdXN0IGEgZGVtbyBhY2Nlc3MgdG9rZW4u
 
{
    "query": "Resource:",
    "limit": 100,
    "start": 0,
    "locale": "en"
}
 
# Response
HTTP/1.1 200 OK
Content-Type: application/json
 
{
    "ticketList": [
        1,
        2,
        3,
        4
    ],
    "hasMore": true,
    "suggestedValues": [
        "First Level Support",
        "Sub 2. Second Level",
        "Sub Ressource 1. Level"
    ],
    "suggestedFields": []
}

# Browser access
http://127.0.0.1:9000/api/ticket/search
 
# Shell access using curl
curl -Ls "http://127.0.0.1:9000/api/ticket/search" \
     --header 'Authorization: Bearer VGhpcyBpcyBqdXN0IGEgZGVtbyBhY2Nlc3MgdG9rZW4u' \
     --header "Content-Type: application/json" \
     --request POST \
     --data '{"query":"Resource:","locale":"en"}'
 
 
# Shell access using curl using username and password
curl -Lsu username:password "http://127.0.0.1:9000/api/ticket/search" \
     --header "Content-Type: application/json" \
     --request POST \
     --data '{"query":"Resource:","locale":"en"}'