2018-06-23 18:17:05 +02:00
|
|
|
# Get a raw message
|
|
|
|
|
2020-04-28 20:00:46 +02:00
|
|
|
{generate_api_description(/messages/{message_id}:get)}
|
2018-06-23 18:17:05 +02:00
|
|
|
|
|
|
|
## Usage examples
|
|
|
|
|
2018-09-17 16:27:32 +02:00
|
|
|
{start_tabs}
|
|
|
|
{tab|python}
|
2018-06-23 18:17:05 +02:00
|
|
|
|
2018-09-17 16:27:32 +02:00
|
|
|
{generate_code_example(python)|/messages/{message_id}:get|example}
|
|
|
|
|
|
|
|
{tab|curl}
|
2018-06-23 18:17:05 +02:00
|
|
|
|
2019-10-02 12:33:29 +02:00
|
|
|
{generate_code_example(curl)|/messages/{message_id}:get|example}
|
2018-06-23 18:17:05 +02:00
|
|
|
|
2018-09-17 16:27:32 +02:00
|
|
|
{end_tabs}
|
2018-06-23 18:17:05 +02:00
|
|
|
|
|
|
|
## Arguments
|
|
|
|
|
|
|
|
{generate_api_arguments_table|zulip.yaml|/messages/{message_id}:get}
|
|
|
|
|
|
|
|
## Response
|
|
|
|
|
|
|
|
#### Return values
|
|
|
|
|
2020-05-20 11:57:57 +02:00
|
|
|
{generate_return_values_table|zulip.yaml|/messages/{message_id}:get}
|
2018-06-23 18:17:05 +02:00
|
|
|
|
|
|
|
#### Example response
|
|
|
|
|
|
|
|
A typical successful JSON response may look like:
|
|
|
|
|
|
|
|
{generate_code_example|/messages/{message_id}:get|fixture(200)}
|
|
|
|
|
|
|
|
An example JSON response for when the specified message does not exist or it
|
|
|
|
is not visible to the user making the query (e.g. it was a PM between other
|
|
|
|
two users):
|
|
|
|
|
|
|
|
{generate_code_example|/messages/{message_id}:get|fixture(400)}
|