enable redirect for few testing endpoints and one category

Author: B4nan

apify-api/openapi/components/tags.yaml

@@ -143,6 +143,7 @@
   x-parent-tag-name: Actors
   x-legacy-doc-urls:
   - '#/reference/actors/run-collection'
+  - '#tag/ActorsRun-collection'
   x-trait: 'true'
 - name: Actors/Run actor synchronously
   x-displayName: Run actor synchronously

apify-api/openapi/paths/actors/acts@{actorId}@run-sync.yaml

@@ -5,29 +5,22 @@ post:
   description: |
     Runs a specific Actor and returns its output.
 
-
     The POST payload including its `Content-Type` header is passed as `INPUT` to
     the Actor (usually <code>application/json</code>).
-
     The HTTP response contains Actors `OUTPUT` record from its default
     key-value store.
 
-
     The Actor is started with the default options; you can override them using
     various URL query parameters.
-
     If the Actor run exceeds 300<!-- MAX_ACTOR_JOB_SYNC_WAIT_SECS --> seconds,
     the HTTP response will have status 408 (Request Timeout).
 
-
     Beware that it might be impossible to maintain an idle HTTP connection for a
     long period of time, due to client timeout or network conditions. Make sure your HTTP client is
     configured to have a long enough connection timeout.
-
     If the connection breaks, you will not receive any information about the run
     and its status.
 
-
     To run the Actor asynchronously, use the [Run
     Actor](#/reference/actors/run-collection/run-actor) API endpoint instead.
   operationId: act_runSync_post
@@ -42,9 +35,9 @@ post:
         example: janedoe~my-actor
     - name: outputRecordKey
       in: query
-      description: |-
+      description: |
         Key of the record from run's default key-value store to be returned
-                                                     in the response. By default, it is `OUTPUT`.
+        in the response. By default, it is `OUTPUT`.
       style: form
       explode: true
       schema:
@@ -103,12 +96,9 @@ post:
       description: |
         Specifies optional webhooks associated with the Actor run, which can be
         used to receive a notification
-
         e.g. when the Actor finished or failed. The value is a Base64-encoded
         JSON array of objects defining the webhooks. For more information, see
-
-        [Webhooks
-        documentation](https://docs.apify.com/platform/integrations/webhooks).
+        [Webhooks documentation](https://docs.apify.com/platform/integrations/webhooks).
       style: form
       explode: true
       schema:
@@ -143,9 +133,8 @@ post:
           example:
             error:
               type: run-failed
-              message: >-
-                Actor run did not succeed (run ID: 55uatRrZib4xbZs, status:
-                FAILED)
+              message: |
+                Actor run did not succeed (run ID: 55uatRrZib4xbZs, status: FAILED)
     '408':
       description: ''
       headers: {}
@@ -161,29 +150,24 @@ post:
   x-legacy-doc-urls:
     - https://docs.apify.com/api/v2#/reference/actors/run-actor-synchronously/with-input
     - https://docs.apify.com/api/v2#/reference/actors/with-input
+    - https://docs.apify.com/api/v2#tag/ActorsRun-actor-synchronously/operation/act_runSync_post
 get:
   tags:
     - Actors/Run actor synchronously
   summary: Without input
   description: |
     Runs a specific Actor and returns its output.
-
     The run must finish in 300<!-- MAX_ACTOR_JOB_SYNC_WAIT_SECS --> seconds
     otherwise the API endpoint returns a timeout error.
-
     The Actor is not passed any input.
 
-
     Beware that it might be impossible to maintain an idle HTTP connection for a
     long period of time,
-
     due to client timeout or network conditions. Make sure your HTTP client is
     configured to have a long enough connection timeout.
-
     If the connection breaks, you will not receive any information about the run
     and its status.
 
-
     To run the Actor asynchronously, use the [Run
     Actor](#/reference/actors/run-collection/run-actor) API endpoint instead.
   operationId: act_runSync_get
@@ -198,9 +182,9 @@ get:
         example: janedoe~my-actor
     - name: outputRecordKey
       in: query
-      description: |-
+      description: |
         Key of the record from run's default key-value store to be returned
-                                                     in the response. By default, it is `OUTPUT`.
+        in the response. By default, it is `OUTPUT`.
       style: form
       explode: true
       schema:
@@ -259,12 +243,9 @@ get:
       description: |
         Specifies optional webhooks associated with the Actor run, which can be
         used to receive a notification
-
         e.g. when the Actor finished or failed. The value is a Base64-encoded
         JSON array of objects defining the webhooks. For more information, see
-
-        [Webhooks
-        documentation](https://docs.apify.com/platform/integrations/webhooks).
+        [Webhooks documentation](https://docs.apify.com/platform/integrations/webhooks).
       style: form
       explode: true
       schema:
@@ -308,3 +289,4 @@ get:
   x-legacy-doc-urls:
     - https://docs.apify.com/api/v2#/reference/actors/run-actor-synchronously/without-input
     - https://docs.apify.com/api/v2#/reference/actors/without-input
+    - https://docs.apify.com/api/v2#tag/ActorsRun-actor-synchronously/operation/act_runSync_get