Skip to content
Qualia Docs

Issues_ListReplies

GET
/v1/accounts/{account}/datasets/{dataset}/issues/{issue}/replies
 
curl --request GET \
  --url https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/issues/example/replies \
  --header 'X-API-Key: <X-API-Key>'

Lists the replies under an issue, oldest first.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
account
required
string

The account id.

dataset
required
string

The dataset id.

issue
required
string

The issue id.

Query Parameters

Section titled “Query Parameters ”
pageSize
integer format: int32

At most this many replies; 0 means 100, the maximum is 500.

pageToken
string

From a previous response’s next_page_token.

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

Response for Issues.ListReplies.

object
replies

One page of replies.

Array<object>

A reply under an issue or a note.

object
name

Accounts/{account}/datasets/{dataset}/issues/{issue}/replies/{reply}

string
text
required

What was said.

string
author

Who said it.

object
kind

What kind of actor it is.

string format: enum
Allowed values: KIND_UNSPECIFIED PERSON VALIDATION RULE MODEL OPERATOR SYSTEM
user

The person’s user id when kind is PERSON; empty otherwise.

string
displayName

The person’s display name at the time, for rendering without a lookup.

string
agent

The rule code, or the model id (e.g. “gemini-robotics-er”), when not a person.

string
run

The run a model or rule finding came from, when it has one.

string
apiKey

The API key’s id when a person acted through one; empty for a session. Never the key itself.

string
attribution

Signed identity evidence recorded with the change, kept apart from the principal above. Unset on older records and wherever none was signed.

object
authentication

How the principal authenticated.

string format: enum
Allowed values: AUTHENTICATION_UNSPECIFIED SESSION API_KEY SERVICE
initiator

The user id of a person verified as starting the work: the person of a session, or the person a trusted service’s signed job record names. Empty when nobody was verified.

string
initiatorDisplayName

The initiator’s display name at the time, never their email.

string
credentialCreator

The user id of the key’s creator at the time. Not who used the key.

string
credentialOwner

Who owned the key at the time.

string format: enum
Allowed values: CREDENTIAL_OWNER_UNSPECIFIED PERSON SPACE
credentialOwnerSpace

The owning space’s id (a workspace or the organization) when credential_owner is SPACE.

string
createTime

When.

string format: date-time
updateTime

When last edited.

string format: date-time
etag

Sent back on UpdateReply; a stale etag fails with ABORTED.

string
nextPageToken

Empty on the last page.

string
Example 
{
  "replies": [
    {
      "author": {
        "kind": "KIND_UNSPECIFIED",
        "attribution": {
          "authentication": "AUTHENTICATION_UNSPECIFIED",
          "credentialOwner": "CREDENTIAL_OWNER_UNSPECIFIED"
        }
      }
    }
  ]
}

default

Section titled “default ”

Default error response

Media type application/json

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object
code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32
message

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

string
details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object
@type

The type of the serialized message.

string
key
additional properties
any
Example generated
{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}