September 22, 2026: The Abuse API v2 now returns more granular ticket closeReason values
View as MarkdownSeptember 22, 2026API
Abuse
Changed
The Abuse API v2 now returns more granular closeReason values, so you can better understand the outcome of a closed ticket. The closeReason field on GET /v2/abuse/tickets/{ticketId} now resolves to one of actioned, false_positive, not_actionable, forwarded_complaint, reclassified, not_registered_hosted_here, closed_expired, or invalid_report.
The field remains optional and is only present once a ticket is closed. Existing integrations that read closeReason continue to work and require no changes, though you may wish to map the additional values.
Links
- Abuse API reference: updated values for
closeReasoninAbuseTicket
Last updated on
How is this guide?