Twitter API missing explicit TLS certificate validation error detail

Goal: obtain granular TLS validation failure reasons from Twitter API responses to differentiate expired, untrusted, or hostname‑mismatch certificates.

Constraint: the API currently maps any handshake_failure to a generic HTTP 400/5xx with a vague “Invalid request” message, and there is no option to request detailed error codes or to supply custom trust stores. Uncertainty: whether an undocumented header, query parameter, or diagnostic mode could expose such details.

Is there a way to enable detailed TLS error codes in Twitter API responses? Can developers request additional validation details via a specific header or query parameter? Does Twitter provide any alternative endpoint or diagnostic mode that returns certificate validation specifics?