Skip to main content
    Ivy Biosciences Docs/Call the platform/API/Reference/Reference/Audit/GET /audit/chat-chain/{chatId}

    GET /audit/chat-chain/{chatId}

    Verify a chat's record chain — Re-checks the tamper-evident hash chain of one chat you can access and reports where, if anywhere, it stops matching.

    Auth: required. Send an ivy_ API key (Authorization: Bearer ivy_…), a signed-in session token (Authorization: Bearer …) or the session cookie (browser sessions). See Authentication.

    Re-checks the tamper-evident hash chain of one chat you can access and reports where, if anywhere, it stops matching. A broken chain is returned as a normal 200 with status set to broken; it is a verdict, not an error.

    A chat that does not exist and a chat you cannot access both answer 404. Verification is limited per user, so repeated calls can return 429 with a Retry-After header.

    Request

    Path parameters

    chatIdstring (uuid)

    Chat UUID.

    Responses

    200 OK

    Verification verdict for the chat

    Response shape:

    chatIdstring (uuid)
    statusenum ("broken" | "no_record" | "not_verifiable" | "verified_partial" | "verified")

    verified: every row matched. verified_partial: every checked row matched, but some could not be checked or no committed last event proves that no rows are missing from the end. broken: the chain stopped matching. no_record: the chat has no chained rows. not_verifiable: the chat could not be graded.

    verifiedboolean

    True only when status is verified.

    checkedRowsinteger
    notVerifiableRowsinteger
    headHashstring

    Hash at the head of the partition holding the newest chained row.

    firstBreakAtobject
    partitionsobject[]
    partitionsTruncatedboolean

    True when the chat has more partitions than are listed.

    verifiedAtstring (date-time)
    keyedboolean

    False when the chain was checked with plain SHA-256 because no deployment key is configured.

    linkedGuestChainsobject[]

    Present only when the chat continues guest chats you claimed at sign-up: one verdict per claimed guest chat. status, verified and the row counts above then grade the whole record, the chat and every claimed guest chat together.

    400 Bad Request

    Invalid request

    Response shape: object

    401 Unauthorized

    Authentication required

    Response shape: object

    404 Not Found

    Resource not found

    Response shape: object

    429 Too Many Requests

    Rate limit exceeded

    Response shape: object

    curl -X GET 'https://ivybiosciences.com/api/audit/chat-chain/{chatId}' \
      -H "Authorization: Bearer $IVY_API_KEY"

    Was this page helpful?

    Loading...