getThreadEntry

A Graze API GET request that returns a thread entry specified using the thread entry ID. Threads are comments or 'story activity' on Situations.

Back to Graze API EndPoint Reference.

Request arguments

Endpoint getThreadEntry takes the following request arguments:

Name	Type	Required	Description
`auth_token`	String	No	A valid `auth_token` returned from the `authenticate` request. Alternatively, basic authenticate headers can be used in place of this parameter. See the authenticate endpoint for more information and usage examples.
`entry_id`	Number	Yes	Thread entry ID.

Response

Endpoint getThreadEntry returns the following response:

Type	Description
HTTP Code	HTTP status or error code indicating request success or failure. See HTTP status code definitions for more information.

Successful requests return an array of JSON objects containing the following:

Name	Type	Description
`entry_id`	Number	Thread entry unique ID.
`sig_id`	Number	Situation ID.
`thread_id`	String	Thread identifier. Can be either `support` or `end user`.
`standard_thread`	String	Standard thread.
`status`	Number	Situation status.
`timed_at`	Number	Timestamp of the thread entry.
`uid`	Number	User ID.
`did`	Number	Department ID of the user.
`entry`	String	Text of the thread entry.
`mmid`	Number	Multimedia database reference of embedded resource.

Examples

The following examples demonstrate typical use of endpoint getThreadEntry:

Request example

Example cURL request to return thread entry with entry ID "1":

curl -G -u graze:graze -k -v "https://localhost/graze/v1/getThreadEntry" \
--data-urlencode "entry_id=1"

Response example

Example response returning thread entry with ID "1" on thread "Support":

{
    "entry_id": 1,
    "sig_id": 1,
    "thread_id": "Support",
    "standard_thread": "Support",
    "status": 1,
    "timed_at": 1586874842,
    "uid": 3,
    "did": 1,
    "entry": "My thread entry",
    "mmid": -1
}

In this section: