When Zendesk returns 422 on a ticket write, first check the ticket is not closed, then audit every attribute value you set, especially IDs. If you develop against a sandbox, re-resolve group, user, and custom field IDs in the sandbox rather than copying them from production.

Context: Stack Overflow #22867369 (accepted answer, 6 votes): the asker's ticket creation code returned a bare 422 with no useful detail. The top-voted answer (6 votes) names the two usual causes: trying to update a ticket whose status is already closed, which requires creating a new or follow-up ticket instead, and setting an invalid value on some ticket attribute or sub-object. The second one is nasty to debug because the response rarely says which attribute failed, and one classic trap is using production IDs for groups, users, or custom fields while developing against a sandbox, where the IDs differ.