Skip to content

Commit bac372b

Browse files
committed
feat(docs): update descriptions of all endpoint
1 parent 5f96ed7 commit bac372b

22 files changed

+105
-50
lines changed

docs/api-reference/api-keys/create-an-api-key.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ api:
2020
<span class="font-medium">POST</span> /api_keys
2121
</p>
2222

23-
Creates a new API key and returns the actual key.
23+
**Creates** a new API key and returns the actual key.
2424

2525
<Badge type="warning" text="Note" vertical="middle"/> For security reasons, the
2626
API key will only be returned once after its creation.

docs/api-reference/api-keys/delete-an-api-key-by-id.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,14 @@ api:
2020
<span class="font-medium">DELETE</span> /api_keys/{api_key_id}
2121
</p>
2222

23-
Updates an api key by id. Requires the id of the target api to be passed via path parameter.
24-
Returns `404` if no api key was found with the given `api_key_id`.
23+
**Deletes** an api key by id. **Requires** the target
24+
`api_key_id` as a path parameter.
25+
26+
A valid `api_key_id` is one that was returned by the
27+
[api key creation endpoint](/api-reference/api-keys/create-an-api-key.html).
28+
If no api key can be found with the given `api_key_id`, the endpoint returns status `404`.
29+
30+
Returns `404` if no api key was found with the given `api_key_id`.
2531

2632
<Badge type="danger" text="Warning" vertical="middle"/> As a result of calling this endpoint
2733
<strong>the target api key will be deleted.</strong>

docs/api-reference/api-keys/get-all-api-keys.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,11 @@ api:
2020
<span class="font-medium">GET</span> /api_keys
2121
</p>
2222

23-
Returns all API keys created
23+
**Returns** all API keys created
2424
by the [create api key endpoint](/api-reference/api-keys/create-an-api-key.html).
2525

26-
All returned keys are redacted. Thus, the endpoint never returns the actual key value. The endpoint
27-
will, however, return meta data of each key like the time it was created and its current status.
26+
All returned keys are redacted. Thus, the endpoint never returns the actual key value. The endpoint,
27+
however, returns meta data of each key like the time it was created and its current status.
2828

2929
The result may be inconistent as in not update-to-date as results may be cached
3030
for a short period of time.

docs/api-reference/api-keys/get-an-api-key-by-id.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,12 @@ api:
2020
<span class="font-medium">GET</span> /api_keys/{api_key_id}
2121
</p>
2222

23-
Returns an api key by id. The api key will be identified by the required `api_key_id` path parameter.
24-
In case a key cannot be found, the endpoint will return `404`.
23+
**Returns** an api key by id. **Requires** the target
24+
`api_key_id` as a path parameter.
25+
26+
A valid `api_key_id` is one that was returned by the
27+
[api key creation endpoint](/api-reference/api-keys/create-an-api-key.html).
28+
If no api key can be found with the given `api_key_id`, the endpoint returns status `404`.
2529

2630
All returned keys are redacted. Thus, the endpoint never returns the actual key value. The endpoint
2731
will, however, return meta data of a key like the time it was created and its current status.

docs/api-reference/api-keys/update-an-api-key-by-id.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,16 @@ api:
2020
<span class="font-medium">PUT</span> /api_keys/{api_key_id}
2121
</p>
2222

23-
Updates an api key by id. Requires the id of the target api to be passed via path parameter.
23+
**Updates** an api key by id. **Requires** the target
24+
`api_key_id` as a path parameter.
2425

25-
Returns `404` if no api key was found with the given `api_key_id`.
26+
A valid `api_key_id` is one that was returned by the
27+
[api key creation endpoint](/api-reference/api-keys/create-an-api-key.html).
28+
If no api key can be found with the given `api_key_id`, the endpoint returns status `404`.
29+
30+
Returns `404` if no api key was found with the given `api_key_id`.
31+
32+
Only mutable properties like `name` can be updated.
2633

2734
::: tip Authentication
2835
**The target organization for this request will be determined by the supplied access token.**

docs/api-reference/organizations/create-an-api-client.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,10 +20,12 @@ api:
2020
<span class="font-medium">POST</span> /api_clients
2121
</p>
2222

23-
Creates a new api client. **An api client groups resources like queues, listeners and messages**.
23+
**Creates a new api client**.
24+
25+
**An api client groups resources like queues, listeners and messages**.
2426
Users who need direct acces to the resources can be assigned to an organizations, too.
2527

26-
<Badge type="get" text="Info" vertical="middle"/> In this context an api client and an organization can be used synonymously.
28+
<Badge type="get" text="Info" vertical="middle"/> In this context an api client and an organization can be used synonymously.
2729

2830
::: tip Authentication
2931
**The target organization for this request will be determined by the supplied access token.**

docs/api-reference/queue-listeners/add-a-listener-to-a-queue.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,12 @@ api:
2020
<span class="font-medium">POST</span> /queues/{queue_id}/listeners
2121
</p>
2222

23-
Creates a new listener for a queue associated with the current organization. The `queue_id` path parameter
24-
must point to an existing queue created by [add a queue endpoint](/api-reference/queues/create-a-queue.html).
23+
**Creates** a new listener for a queue. **Requires** the
24+
target `queue_id` as a path parameter.
25+
26+
A valid `queue_id` is one that was returned by the
27+
[queue creation endpoint](/api-reference/queues/create-a-queue.html).
28+
If no queue with the given `queue_id` can be found, the endpoint returns status `404`.
2529

2630
This endpoint returns the listeners's unique identifier, the `listener_id`. This identifier
2731
must be passed to the following listener endpoints to update or delete the listener.

docs/api-reference/queue-listeners/delete-a-listener-by-id.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,13 @@ api:
2020
<span class="font-medium">DELETE</span> /queues/{queue_id}/listeners/{listener_id}
2121
</p>
2222

23-
Deletes a listener by id. To identify the target listener a `queue_id` and a `listener_id` must be passed as a path parameter.
23+
**Deletes** a listener by id. Requires a valid `queue_id` and `listener_id` as path parameters.
2424
If no queue or listener with the given ids can be found, the endpoint returns status `404`.
2525

26+
A valid `queue_id` is one that was returned by the
27+
[queue creation endpoint](/api-reference/queues/create-a-queue.html). The `listener_id` is the one
28+
returned by the [create listener endpoint](/api-reference/queue-listeners/add-a-listener-to-a-queue.html).
29+
2630
<Badge type="danger" text="Warning" vertical="middle"/> As a result of calling this endpoint
2731
<strong>the target listener will be deleted and sent to the shadow realm</strong>. This process cannot be reverted.
2832

docs/api-reference/queue-listeners/get-a-listener-by-id.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,12 @@ api:
2020
<span class="font-medium">GET</span> /queues/{queue_id}/listeners/{listener_id}
2121
</p>
2222

23-
Returns a listener by id. Requires a valid `queue_id` and `listener_id` as prerequisite.
23+
**Returns** a queue listener by id. Requires a valid `queue_id` and `listener_id` as path parameters.
2424
If no queue or listener with the given ids can be found, the endpoint returns status `404`.
2525

26-
Use [this endpoint](/api-reference/queues/create-a-queue.html) to create a queue, and
27-
[this endpoint](/api-reference/queue-listeners/add-a-listener-to-a-queue.html) to create a listener.
26+
A valid `queue_id` is one that was returned by the
27+
[queue creation endpoint](/api-reference/queues/create-a-queue.html). The `listener_id` is the one
28+
returned by the [create listener endpoint](/api-reference/queue-listeners/add-a-listener-to-a-queue.html).
2829

2930
The result may be inconistent as in not update-to-date as results may be cached
3031
for a short period of time.

docs/api-reference/queue-listeners/get-all-listeners.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,9 @@ api:
2020
<span class="font-medium">GET</span> /listeners
2121
</p>
2222

23-
Returns the list of all listeners associated with the current organization. Use this method
24-
to get an overview of all listeners created via the
23+
**Returns** the list of all listeners.
24+
25+
Use this method to get an overview of all listeners created via the
2526
[add a listener to a queue endpoint](/api-reference/queue-listeners/add-a-listener-to-a-queue.html).
2627

2728
As this endpoint is not bound to a specific queue, it will return **all listeners**

0 commit comments

Comments
 (0)