No, I'm afraid the JSON output for certificate identity searches is intentionally undocumented. This is because it was implemented essentially by accident(!), and I don't regard it as a stable API.
My long-term plan has been to co-ordinate with other CT log monitor operators to produce a standard API for querying CT log monitor services, but I don't know if/when this might ever happen.