API integration
Expand your
Helpdesk
integrations with the
eDesk
API integration.
superAI
list_all_edesk_contacts
List contacts in eDesk. Returns id, channel_id, client_id, full_name, phone_number, and email fields…
update_a_edesk_tag_by_id
Update a tag in eDesk using id. Returns fields: id (tag identifier), name (tag name), active (status…
delete_a_edesk_tag_by_id
Delete a tag in eDesk. Requires id. Returns ok (operation status) and message (confirmation details)…
get_single_edesk_tag_by_id
Get details of a specific tag in eDesk by id. Returns id, name, active, tag_group_id, color, and ico…
create_a_edesk_tag
Create a new tag in eDesk. Requires name and tag_group_id. Returns id, name, active, tag_group_id, c…
list_all_edesk_tags
List tags in eDesk. Returns tag fields id, name, active, tag_group_id, color, and icon in the respon…
delete_a_edesk_ticket_by_id
Delete a ticket in eDesk. Requires id. Returns ok (operation success) and message (confirmation deta…
create_a_edesk_ticket
Create a new ticket in eDesk. Requires subject, channel_id, and status. Returns id, subject, channel…
update_a_edesk_ticket_by_id
Update a ticket in eDesk. Requires id. Returns id, subject, channel_id, status, sales_order_id, exte…
get_single_edesk_ticket_by_id
Get details of a ticket in eDesk. Requires id. Returns fields such as id, subject, status, created_a…
list_all_edesk_tickets
List tickets in eDesk. Returns ticket fields: id, subject, channel_id, status, sales_order_id, exter…
list_all_edesk_users
List users in eDesk. Returns id, name, email, active, username, and role for each user.
Enhanced
eDesk
with AI Capabilities
Unified APIs for
eDesk
Skip writing code for every integration. Save time by using Truto's category-specific Unified APIs. You can use the schema we provide out of the box or customize and override the mappings to suit your needs with AI.
Collections
Tickets and contacts can be grouped into Collections. Collection resource usually maps to the various grouping systems used in the underlying product. Some examples are lists, projects, epics, etc. Yo…
Unified Ticketing API
Comments
Comments represent the communication happening on a Ticket, both between a User and a Contact and the internal things like notes, private comments, etc. A Ticket can have one or more Comments.
Unified Ticketing API
Contacts
Contact represent the external people you are in contact with. These could be customers, leads, etc. Contacts can be associated with an Account if the underlying product supports it.
Unified Ticketing API
Tags
Tags represent a common classification approach used in various ticketing systems. A Ticket may have one or more Tags associated with them.
Unified Ticketing API
Tickets
Core resource which represents some work that needs to be carried out. Tickets are usually mapped to issues, tasks, work items, etc. depending on the underlying product.
Unified Ticketing API
Ticket status
Ticket Status represents the completion level of the Ticket. Some products provide customizing the Ticket Status.
Unified Ticketing API
Users
Users represent the people using the underlying ticketing system. They are usually called agents, team members, admins, etc.
Unified Ticketing API
Workspaces
Workspaces represent the top-level subdivision in a ticketing system. They usually have their own set of settings, tickets, statuses, priorities and users. Some of the usual terminologies used by the…
Unified Ticketing API
Proxy API for
eDesk
✨ Powered by AI
Customize the mappings as you need using AI.
Build your own unified API from scratch, aided by AI.
We have been able to dramatically accelerate our GTM timeline by several months as a result of Truto. The devs at Truto worked with us to build a unified API structure with our team so that we have a solid base for future integrations as well. The support has been very quick to respond to our inquiries and provide timely resolutions for our requests.
Josh Benson,
CEO of Omnitrain