[yasser-aboelgheit-intercom]

Why?

Deleting a conversation, attaching or detaching a contact, and converting a conversation to a ticket all return a 400 with code side_conversation when the ID is a side conversation, but the reference doesn't list it. The WhatsApp status errors were shown as {type: error, message} when the API returns an error.list, and the WhatsApp message status endpoint can also return the 403 plan error. The phone call redirect errors showed a placeholder 422 key and didn't cover the 401 returned when the workspace can't use the feature.

How?

Add the side_conversation 400 example to the four conversation endpoints, give the WhatsApp status 400 and 500 examples the error.list shape with their real codes, and add the 403 to the WhatsApp message status endpoint. For POST /phone_call_redirects, show the 422 keys from phone number validation (invalid_phone_number, landline_phone, twilio_settings), describe the 400 as a failed phone number lookup or SMS send, and add the feature 401, in both 2.17 and Preview.

_{Generated with Claude Code}

[markdennis22]

Thanks Yasser, the new and changed error examples match what the API returns.

I compared both files against main, checked the 2.17 and Preview edits are the same, ran fern check (no new errors or warnings), and checked each example against the API's behaviour. The only Preview SDK change is the four added error classes, and it's additive.

Approving.

~ Automated via Claude