Ticket management
Tickets organize each video call around a workflow.
Tickets in the Apizee API represent the entry point for initiating and managing a remote assistance session espacially when it requires state management. The API allows you to create, retrieve, update, and delete individual tickets, as well as list multiple tickets.
Tickets' state can take several values:
new
Ticket has been created but not yet processed.
open
Ticket is available and ready to be assigned or handled.
invited
Guest has been invited to join the session but not yet connected.
inprogress
Session or ticket handling is currently ongoing.
done
Work on the ticket is completed; resolution reached.
closed
Ticket is formally closed and archived; no further action possible.
rejected
Ticket was refused or not accepted for processing.
declined
Invitation or request was refused by the guest.
expired
Ticket validity period ended without resolution.
cancelled
Ticket was withdrawn before completion by the agent or system.
Create a Ticket
Use this operation to open a new assistance request. Typical steps:
Provide the required parameters such as ticket type, related enterprise, and guest/agent information.
(Optional) Select the Service you want the ticket to be created in. By default, the ticket will be created in the preferred service defined in the cloud portal.
(Optional) set an initial state (
new,open, etc.) or metadata.Receive the created ticket details in the response, including its unique
idand join links.
When to use:
Starting a new remote session with a customer.
Preparing a session link to be sent by your own channel (email, chat, etc.).
Recipient name (note: not applicable to assistance multi-participants)
Recipient phone numbers, separated by a comma [example: +33612345678,+33787654321] *required field if no email provided
Recipient emails, separated by a comma [example: paul@apizee.com,jean@apizee.com], cannot be a generic mailbox or shared email address *required field if no phone number provided
Set the language of the notification template.
Ticket type
Email subject
The reference of the ticket.
The description of the ticket.
The user group ID of agents allowed to treat the ticket.
Username or ID of the agent allowed to treat the ticket.
If the invitation needs to be sent immediatly set this field to '1','true' or 'TRUE'.
0Email and sms invitation template that the agent will receive.
email and sms invitation template that the requestor will receive
For Video assistance multi-participants invitation, send conference invitation to the organizer (default: true)
When the ticket will take place. A given ISO 8601 compliant UTC date (format: 2020-01-01T15:00:00Z).
Set a duration (in minutes).
30Activate an email invite reminder (in minutes).
The first name of the recipient (note: not applicable to assistance multi-participants).
The company of the recipient(note: not applicable to assistance multi-participants).
The gender of the recipient (note: not applicable to assistance multi-participants).
The country of the recipient. A given ISO 3166-1 alpha-2 code, example: FR (note: not applicable to assistance multi-participants).
Set the service in which the ticket will be associated (key format: sfa6mdbzx9vigfvryihfokt9khux8qan).
An application can ask for additional scopes by listing the requested scope names.
Good case
Different kind of responses
Get details from a Ticket
Retrieve details of an existing ticket by its id.
This operation returns full metadata: state, participants, creation/update timestamps, and any associated resources.
When to use:
Checking the current status of a session.
Displaying ticket details in your own interface.
Ticket-based resources
Beyond basic ticket CRUD operations, the API provides additional endpoints to retrieve related resources or export ticket data.
Get Ticket Medias
Endpoint: GET /api/v3/tickets/{ticketId}/medias
Retrieve the list of all media files linked to a specific ticket (such as snapshots, uploaded documents, or recordings).
When to use:
Displaying media captured during a session in your own application.
Allowing agents or supervisors to review session-related files.
ID of the wanted ticket
Limit result set to medias assigned one or more statuses.
completedPossible values: Offset the result set by a specific number of items.
Maximum number of items to be returned in result set.
10Limit response to media created after a given ISO 8601 compliant UTC date (format: 2020-01-01T15:00:00Z).
Limit response to media created before a given ISO 8601 compliant UTC date (format: 2020-01-01T16:00:00Z).
Limit results to those matching a string.
Sort collection by object attribute.
datePossible values: Order sort attribute ascending or descending.
descPossible values: Limit result set to attachments of a particular media type.
Limit result set to media assigned to a specific tag.
Limit result set to media attached to a specific user ID (set 'all' to limit result to the enterprise, admin role required).
Limit result set to media attached to a specific user group ID.
Limit result set to attachments of a particular source type.
Download the tickets medias
Name of the downloaded file without extension
Good case
Good case
Get Ticket Events
Endpoint: GET /api/v3/tickets/{ticketId}/events
Retrieve a chronological list of all events associated with a ticket. Events may include invitations sent, session starts, status changes, and other tracked actions.
When to use:
Auditing the lifecycle of a ticket.
Building a session timeline for reporting or troubleshooting.
ID of the wanted ticket
Good case
Forbidden
Not found case
Export Ticket Data
Endpoint: POST /api/v3/tickets/{ticketId}/export
Export the complete ticket data set (including metadata, events, and media) in a downloadable format.
A successful call returns a resource you can use to fetch the exported file.
When to use:
Archiving a ticket for compliance or contractual purposes.
Sharing a complete session record with an external system.
ID of the wanted ticket
Optional export format.
Optional, allows adding the ticket's timeline (list of events).
Successful operation
Bad request
Update a Ticket
Modify certain properties of a ticket (for example, change its state, update agent assignment, or adjust metadata). Partial updates are supported—only send the fields you want to change.
When to use:
Transitioning a ticket through its lifecycle (
open→inprogress→done).Changing the assigned agent mid-session.
The Ticket ID.
Username or ID of the agent allowed to treat the ticket.
The state of the ticket.
openPossible values: The reference of the ticket.
The description of the ticket.
The subject of the ticket.
The user group ID of agents allowed to treat the ticket.
No content
Bad request
Unauthorized
Forbidden
404 Resource Not Found
No content
Delete a Ticket
Remove a ticket from the system by its id.
This is irreversible and should only be done when you are certain the ticket is no longer needed.
When to use:
Cleaning up expired or test tickets.
Cancelling sessions before they start.
Use to delete a ticket by ID.
The Ticket ID.
Good case
Good case
List Tickets
Retrieve a paginated list of tickets. Supports filters (by state, date, enterprise, etc.) to narrow down results.
When to use:
Building dashboards or reporting views.
Fetching active tickets for a specific enterprise or agent.
Limit response to tickets created after a given ISO 8601 compliant UTC date (format: 2020-01-01T15:00:00Z).
Limit response to tickets created before a given ISO 8601 compliant UTC date (format: 2020-01-01T16:00:00Z).
Limit response to tickets started at or after a given ISO 8601 compliant UTC date (format: 2020-01-01T16:00:00Z).
Limit response to tickets ended at or before a given ISO 8601 compliant UTC date (format: 2020-01-01T15:00:00Z).
Limit results to those matching a string.
Sort collection by object attribute.
start_timePossible values: Order sort attribute ascending or descending.
descPossible values: Maximum number of items to be returned in result set.
10Offset the result set by a specific number of items.
Limit result set to tickets attached to a specific user ID (set 'all' to limit result to the enterprise, admin role required). Current user by default.
Limit result set to tickets attached to a specific user group ID.
Limit result set to tickets with a specific reference.
Limit result set to tickets with a specific type.
Limit result set to tickets attached to a specific requestor (contact) ID.
An application can ask for additional scopes by listing the requested scope names.
Limit results to a given service (key format: sfa6mdbzx9vigfvryihfokt9khux8qan). Default service by default.
OK
OK
Last updated