2018-06-21 15:23:10 +02:00
|
|
|
# Fetch a development API key
|
|
|
|
|
2020-04-28 20:00:46 +02:00
|
|
|
{generate_api_description(/dev_fetch_api_key:post)}
|
2018-06-21 15:23:10 +02:00
|
|
|
|
|
|
|
## Usage examples
|
|
|
|
|
2018-10-18 00:14:30 +02:00
|
|
|
{start_tabs}
|
|
|
|
{tab|curl}
|
2018-06-21 15:23:10 +02:00
|
|
|
|
2019-10-14 12:49:04 +02:00
|
|
|
{generate_code_example(curl)|/dev_fetch_api_key:post|example}
|
2018-06-21 15:23:10 +02:00
|
|
|
|
2018-10-18 00:14:30 +02:00
|
|
|
{end_tabs}
|
2018-06-21 15:23:10 +02:00
|
|
|
|
|
|
|
## Arguments
|
|
|
|
|
|
|
|
{generate_api_arguments_table|zulip.yaml|/dev_fetch_api_key:post}
|
|
|
|
|
|
|
|
## Response
|
|
|
|
|
|
|
|
#### Return values
|
|
|
|
|
2020-05-20 11:57:57 +02:00
|
|
|
{generate_return_values_table|zulip.yaml|/dev_fetch_api_key:post}
|
2018-06-21 15:23:10 +02:00
|
|
|
|
|
|
|
#### Example response
|
|
|
|
|
|
|
|
A typical successful JSON response may look like:
|
|
|
|
|
|
|
|
{generate_code_example|/dev_fetch_api_key:post|fixture(200)}
|