customer_service
Organization Domain Match For Ticket
What the deterministic domain lookup makes of this ticket.
Frederick, 2026-08-10: "If every organization already has an email domain that we know what it is, that's deterministic. It should always be able to identify that in any email we receive."
inbound.py already runs this on the way in, so a ticket that could be matched deterministically arrives matched and never reaches this endpoint. What is left is exactly the two cases a human is needed for, and the desk should not make them work either one out for themselves:
- a ticket older than that wiring, whose answer has been sitting in its own body the whole time -- offered here as a one-click match through the SAME match-organization action a manual search ends in, never applied behind their back.
- a domain two organisations share. There is no right answer to pick (delaware.gov is Delaware DOC and Delaware DSCYF), so this returns the ambiguity with both names in it and the person chooses.
Never writes. org_id here is a suggestion; only POST match-organization changes the ticket.
get/api/cs/tickets/{ticket_id}/organization-domain-match
Request
- Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
- URL: https://api.pigeonly.com/api/cs/tickets/{ticket_id}/organization-domain-match
- Auth: none declared
Path parameters
ticket_idstring uuid required
Response
Successful Response
object required
Changes
No recorded changes to this operation across all 1 revision of this API.