How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

freshdesk Tickets API

Manage support tickets including creation, updates, bulk operations, merging, and lifecycle management.

freshdesk Tickets API is one of 17 APIs that Freshdesk publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Tickets. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 14 operations across 11 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://{domain}.freshdesk.com/api/v2.

14 operations 11 paths 5 schemas 1 DELETE5 GET5 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://yourdomain.freshdesk.com/api/v2
Authentication
HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 1

freshdesk Tickets API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — Freshdesk uses API key-based authentication. Pass your API key as the username with any string (e.g. X) as the password using HTTP Basic Authentication.

Paths & Operations 14

Across 11 paths, the API surfaces 14 operations — 1 DELETE, 5 GET, 5 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Tickets 14

Manage support tickets including creation, updates, bulk operations, merging, and lifecycle management.

GET
/tickets
List all tickets
listTickets 9 params → 200401
POST
/tickets
Create a ticket
createTicket body → 201400401
GET
/tickets/{ticket_id}
View a ticket
getTicket 2 params → 200401404
PUT
/tickets/{ticket_id}
Update a ticket
updateTicket 1 param body → 200400401404
DELETE
/tickets/{ticket_id}
Delete a ticket
deleteTicket 1 param → 204401404
PUT
/tickets/{ticket_id}/restore
Restore a deleted ticket
restoreTicket 1 param → 204401404
POST
/tickets/outbound_email
Create an outbound email ticket
createOutboundEmail body → 201400401
GET
/tickets/{ticket_id}/watchers
List watchers on a ticket
listTicketWatchers 1 param → 200401404
POST
/tickets/{ticket_id}/watch
Watch a ticket
watchTicket 1 param → 204401404
GET
/tickets/{ticket_id}/associated_tickets
List associated tickets
listAssociatedTickets 1 param → 200401404
PUT
/tickets/merge
Merge tickets
mergeTickets body → 200400401
POST
/tickets/bulk_update
Bulk update tickets
bulkUpdateTickets body → 202400401
POST
/tickets/bulk_delete
Bulk delete tickets
bulkDeleteTickets body → 202400401
GET
/ticket_fields
List all ticket fields
listTicketFields → 200401

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Ticket (27 properties), TicketCreate (15 properties), Field (12 properties), TicketUpdate (11 properties). Each schema is shown below with its type and property counts.

Ticket
object
27 properties
Field
object
12 properties
TicketUpdate
object
11 properties
TicketCreate
object
15 properties
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

freshdesk-tickets-api-openapi.yml Raw ↑

Other APIs Freshdesk publishes across the network.

Freshdesk Webhook API
Freshdesk App SDK
freshdesk Agents API
freshdesk Business Hours API
freshdesk Companies API
freshdesk Contacts API
freshdesk Conversations API
freshdesk Email Configs API
freshdesk Groups API
freshdesk Products API
freshdesk Roles API
freshdesk Satisfaction Ratings API
Where this information came from

This is an independent, third-party profile of freshdesk Tickets API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.