Create imported ticket
By default this endpoint creates a ticket without attachments. If you want to create a ticket containing attachments:
- Create new import transaction by issuing
POSTrequest to/v1/importedTickets/transactionsendpoint - Upload attachments by issuing
POSTrequest(s) to/v1/importedTickets/attachmentswith propertransactionIDacquired in step 1. The response will contain array withattachmentIDsyou can use in step 3. - Create new ticket issuing
POSTrequest to/v1/importedTicketsendpoint with additionaltransactionIDparameter acquired in step 1
Remarks:
- First event has to be of type
message - Date of first message event is considered ticket creating date
- Events have to be chronologically ordered and in the past
- Events of type
messageandattachmentsare grouped together when the date parameter in both events matchattachment.filesarray contains IDs generated during attachment upload - All uploaded attachments have to be used during ticket import
TransactionIDstays valid for 24 hours- Ticket status can be changed using status event (last such status is used as final status)
- Agent-issued message or attachment requires
agentID,agentNameandisPrivateparameters. Messages without these parameters are considered as requester-issued. These rules concern both message and attachments events.
Authorizations
Use your account ID as the username and your personal access token (PAT) as the password, or pass a Base64-encoded value directly in the Authorization header. For more information, see the personal access tokens guide.
Body
The requester’s email and name.
The ticket subject.
A list of teams that have access to the ticket.
A list of tags.
The team or agent assignment.
-10, 0, 10, 20 The object containing custom fields.
A list of ticket events.
agentID, agentName and isPrivate are required for agent’s message. If these fields are not present, message is from requester.
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
Unique object identifier
"42e113f9-9353-4e89-9f68-69b92f423b0c"
Response
Successful response.
Unique object identifier.
Unique account identifier.
The time of creation.
The creator identifier.
The creator type.
agent, client, system The time of last modification.
The modification author identifier.
The short ticket ID.
The time of last public message.
The parent ticket reference.
The merged ticket reference.
Ticket status
open, pending, onhold, solved, closed -10, 0, 10, 20 The teams that can access the ticket.
Unique object identifier
Ticket requester
A list of people in the loop.
A list of ticket tags.
Unique object identifier
A list of ticket followers (agents).
Unique object identifier
Team / agent assignment
Object with custom fields values, where key is custom fields apiKey.
Has rating request been sent.
Ticket rating
Ticket silo (folder). Please check ticket silos section for more information
tickets, archive, trash, spam - Option 1
- Option 2
- Option 3
- Option 4
The ticket events.
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
- Option 10
- Option 11
- Option 12
- Option 13
- Option 14
- Option 15
- Option 16
- Option 1
- Option 2
The detected language code.