split request queues into 3 sub categories

split request queues into 3 sub-categories
change descriptions for introductory pages to reflect new division
reorganize sidebar further
add missin request queues redirects to ngninx.conf

Author: TC-MO

apify-api/openapi/components/tags.yaml

@@ -236,20 +236,61 @@
   - '#tag/Request-queuesQueue-collection'
   - '#/reference/request-queues/queue'
   - '#tag/Request-queuesQueue'
+  - '#/reference/request-queues/batch-request-operations'
+  - '#tag/Request-queuesBatch-request-operations'
+  description: |
+    This section describes API endpoints to create, manage, and delete request queues.
+
+    Request queue is a storage for a queue of HTTP URLs to crawl, which is typically
+    used for deep crawling of websites where you
+    start with several URLs and then recursively follow links to other pages.
+    The storage supports both breadth-first and depth-first crawling orders.
+
+    For more information, see the [Request queue documentation](https://docs.apify.com/platform/storage/request-queue).
+
+    :::note
+
+    Some of the endpoints do not require the authentication token, the calls
+    are authenticated using the hard-to-guess ID of the queue.
+
+    :::
+- name: Storage/Request queues/Requests
+  x-displayName: Requests- Introduction
+  x-parent-tag-name: Storage
+  x-legacy-doc-urls:
   - '#/reference/request-queues/request-collection'
   - '#tag/Request-queuesRequest-collection'
   - '#/reference/request-queues/request'
   - '#tag/Request-queuesRequest'
+  description: |
+    This section describes API endpoints to create, manage, and delete requests within request queues.
+
+    Request queue is a storage for a queue of HTTP URLs to crawl, which is typically
+    used for deep crawling of websites where you
+    start with several URLs and then recursively follow links to other pages.
+    The storage supports both breadth-first and depth-first crawling orders.
+
+    For more information, see the [Request queue documentation](https://docs.apify.com/platform/storage/request-queue).
+
+    :::note
+
+    Some of the endpoints do not require the authentication token, the calls
+    are authenticated using the hard-to-guess ID of the queue.
+
+    :::
+- name: Storage/Request queues/Requests locks
+  x-displayName: Requests locks - Introduction
+  x-parent-tag-name: Storage
+  x-legacy-doc-urls:
+
   - '#/reference/request-queues/request-lock'
   - '#tag/Request-queuesRequest-lock'
   - '#/reference/request-queues/queue-head'
   - '#tag/Request-queuesQueue-head'
   - '#/reference/request-queues/queue-head-with-locks'
   - '#tag/Request-queuesQueue-head-with-locks'
-  - '#/reference/request-queues/batch-request-operations'
-  - '#tag/Request-queuesBatch-request-operations'
   description: |
-    This section describes API endpoints to create, manage, and delete request queues.
+    This section describes API endpoints to create, manage, and delete request locks within request queues.
 
     Request queue is a storage for a queue of HTTP URLs to crawl, which is typically
     used for deep crawling of websites where you

apify-api/openapi/components/x-tag-groups.yaml

@@ -20,6 +20,8 @@
   - Storage/Datasets
   - Storage/Key-value stores
   - Storage/Request queues
+  - Storage/Request queues/Requests
+  - Storage/Request queues/Requests locks
 - name: Webhooks
   tags:
   - Webhooks/Webhooks

apify-api/openapi/openapi.yaml

@@ -581,18 +581,18 @@ paths:
     $ref: paths/request-queues/request-queues.yaml
   '/v2/request-queues/{queueId}':
     $ref: 'paths/request-queues/request-queues@{queueId}.yaml'
+  '/v2/request-queues/{queueId}/requests/batch':
+    $ref: 'paths/request-queues/request-queues@{queueId}@[email protected]'
   '/v2/request-queues/{queueId}/requests':
     $ref: 'paths/request-queues/request-queues@{queueId}@requests.yaml'
   '/v2/request-queues/{queueId}/requests/{requestId}':
     $ref: 'paths/request-queues/request-queues@{queueId}@requests@{requestId}.yaml'
-  '/v2/request-queues/{queueId}/requests/{requestId}/lock':
-    $ref: 'paths/request-queues/request-queues@{queueId}@requests@{requestId}@lock.yaml'
   '/v2/request-queues/{queueId}/head':
     $ref: 'paths/request-queues/request-queues@{queueId}@head.yaml'
   '/v2/request-queues/{queueId}/head/lock':
     $ref: 'paths/request-queues/request-queues@{queueId}@[email protected]'
-  '/v2/request-queues/{queueId}/requests/batch':
-    $ref: 'paths/request-queues/request-queues@{queueId}@requests@batch.yaml'
+  '/v2/request-queues/{queueId}/requests/{requestId}/lock':
+    $ref: 'paths/request-queues/request-queues@{queueId}@requests@{requestId}@lock.yaml'
   /v2/webhooks:
     $ref: paths/webhooks/webhooks.yaml
   '/v2/webhooks/{webhookId}':

apify-api/openapi/paths/datasets/datasets@{datasetId}@items.yaml

@@ -433,7 +433,7 @@ get:
 post:
   tags:
     - Storage/Datasets
-  summary: Put items
+  summary: Store items
   description: |
     Appends an item or an array of items to the end of the dataset.
     The POST payload is a JSON object or a JSON array of objects to save into the dataset.

apify-api/openapi/paths/key-value-stores/key-value-stores@{storeId}@records@{recordKey}.yaml

@@ -73,7 +73,7 @@ get:
 put:
   tags:
     - Storage/Key-value stores
-  summary: Put record
+  summary: Store record
   description: |
     Stores a value under a specific key to the key-value store.
 

apify-api/openapi/paths/request-queues/request-queues@{queueId}@head.yaml

@@ -1,6 +1,6 @@
 get:
   tags:
-    - Storage/Request queues
+    - Storage/Request queues/Requests locks
   summary: Get head
   description: |
     Returns given number of first requests from the queue.

apify-api/openapi/paths/request-queues/request-queues@{queueId}@[email protected]

@@ -1,6 +1,6 @@
 post:
   tags:
-    - Storage/Request queues
+    - Storage/Request queues/Requests locks
   summary: Get head and lock
   description: |
     Returns the given number of first requests from the queue and locks them for

apify-api/openapi/paths/request-queues/request-queues@{queueId}@requests.yaml

@@ -1,6 +1,6 @@
 get:
   tags:
-    - Storage/Request queues
+    - Storage/Request queues/Requests
   summary: List requests
   description: |
     Returns a list of requests. This endpoint is paginated using
@@ -137,7 +137,7 @@ get:
   x-py-doc-url: https://docs.apify.com/api/client/python/reference/class/RequestQueueClientAsync#list_requests
 post:
   tags:
-    - Storage/Request queues
+    - Storage/Request queues/Requests
   summary: Add request
   description: |
     Adds request to the queue. Response contains ID of the request and info if

apify-api/openapi/paths/request-queues/request-queues@{queueId}@requests@{requestId}.yaml

@@ -1,6 +1,6 @@
 get:
   tags:
-    - Storage/Request queues
+    - Storage/Request queues/Requests
   summary: Get request
   description: Returns request from queue.
   operationId: requestQueue_request_get
@@ -78,7 +78,7 @@ get:
   x-py-doc-url: https://docs.apify.com/api/client/python/reference/class/RequestQueueClientAsync#get
 put:
   tags:
-    - Storage/Request queues
+    - Storage/Request queues/Requests
   summary: Update request
   description: |
     Updates a request in a queue. Mark request as handled by setting
@@ -197,7 +197,7 @@ put:
   x-py-doc-url: https://docs.apify.com/api/client/python/reference/class/RequestQueueClientAsync#update
 delete:
   tags:
-    - Storage/Request queues
+    - Storage/Request queues/Requests
   summary: Delete request
   description: Deletes given request from queue.
   operationId: requestQueue_request_delete

apify-api/openapi/paths/request-queues/request-queues@{queueId}@requests@{requestId}@lock.yaml

@@ -1,6 +1,6 @@
 put:
   tags:
-    - Storage/Request queues
+    - Storage/Request queues/Requests locks
   summary: Prolong request lock
   description: |
     Prolongs request lock. The request lock can be prolonged only by the client
@@ -84,7 +84,7 @@ put:
   x-py-doc-url: https://docs.apify.com/api/client/python/reference/class/RequestQueueClientAsync#prolong_request_lock
 delete:
   tags:
-    - Storage/Request queues
+    - Storage/Request queues/Requests locks
   summary: Delete request lock
   description: |
     Deletes a request lock. The request lock can be deleted only by the client