The ticket creation endpoint now accepts multiple tags. Pass the tag field as a single string, as before, or as an array of tag names or IDs, and every tag that exists in your workspace is applied to the new ticket. Names are matched case-insensitively, unknown entries are ignored, duplicates collapse, and the order you send is the order that's stored.
This matters most for routing. If you tag a ticket with a product and a region, say, any assignment rule scoped to either tag fires, so integrations that create tickets on your behalf can now express the same combinations you'd set by hand in the dashboard. If none of the tags you send resolve, the AI's own classification applies exactly as it did before.
Existing integrations keep working unchanged: a single-string tag behaves identically, and the response still returns the first applied tag in the tag field. A new tags field alongside it lists every applied tag name in order.