Auth
- Auth method
none- Signature detail
- Freshdesk webhooks do not include a request signature by default. Authentication relies on IP allowlisting or a custom token in the URL.
Delivery
- Guarantees
- at-least-once
- Backoff
- Freshdesk retries failed webhook deliveries.
Payload schema (field names + types only)
ticket object required
The ticket that triggered the event.
id integer required
Ticket ID.
subject string required
Ticket subject.
description string | null
HTML description of the ticket.
status integer required
Status code (2=open, 3=pending, 4=resolved, 5=closed).
priority integer
Priority code (1=low, 2=medium, 3=high, 4=urgent).
type string | null
Ticket type (Question, Incident, Problem, Feature Request, etc.).
source integer
Source channel (1=email, 2=portal, 3=phone, etc.).
requester_id integer
ID of the contact who submitted the ticket.
responder_id integer | null
ID of the assigned agent.
group_id integer | null
ID of the assigned group.
due_by string | null
Resolution due date.
fr_due_by string | null
First response due date.
custom_fields object
Custom field values for this ticket.
reply object
The reply or note that was added.
body string
HTML body of the reply.
body_text string
Plain text version of the body.
Notes: Freshdesk webhooks are configured via automation rules rather than a webhook subscription API. Events are trigger conditions; payload shape depends on which rule fires.
Vendor docs