Resolve exact conflicting evidence for a Hover Disputed Detail

GET https://app.hover.team/api/v1/hover/spaces/{space_id}/generated-items/{generated_item_id}/disputed-details/{disputed_detail_id}/evidence

Resolves the ordered evidence subset stored for one field-scoped conflict. The client cannot submit evidence or provider references. Authorization follows the generated root message and its launched Space.

Usage examples

curl -sSX GET -G https://app.hover.team/api/v1/hover/spaces/2/generated-items/3/disputed-details/4/evidence \
    -u EMAIL_ADDRESS:API_KEY

Parameters

Response

Return values

• evidence: (object)[]

  The evidence value. * evidence_ref: string

  The `evidence_ref` value.
  

  • source_ref: string

    The source_ref value. * sender: object

    The sender value. * ref: string

    The `ref` value.
    

    • display_name: string

      The display_name value. * timestamp: string

    The timestamp value. * content: object

    The content value. * text: string | null

    The `text` value.
    

    • voice_transcript: string | null

      The voice_transcript value. * media_description: string | null

      The media_description value. * media: object | null

    The media value. * type: string

    The `type` value.
    

    • mime_type: string | null

      The mime_type value. * byte_size: integer | null

      The byte_size value. * sha256: string | null

      The sha256 value. * available: boolean

      The available value.

Example response(s)

Changes: As of Zulip 7.0 (feature level 167), if any parameters sent in the request are not supported by this endpoint, a successful JSON response will include an ignored_parameters_unsupported array.

A typical successful JSON response may look like:

{
    "evidence": [],
    "msg": "",
    "result": "success"
}