diff --git a/extend/component/deployment/index.md b/extend/component/deployment/index.md
index 238827b3..9154da43 100644
--- a/extend/component/deployment/index.md
+++ b/extend/component/deployment/index.md
@@ -342,10 +342,9 @@ before_script:
   - docker tag $APP_IMAGE:latest $REPOSITORY:test
   - eval $(docker run --rm -e KBC_DEVELOPERPORTAL_USERNAME -e KBC_DEVELOPERPORTAL_PASSWORD -e KBC_DEVELOPERPORTAL_URL quay.io/keboola/developer-portal-cli-v2:latest ecr:get-login $KBC_DEVELOPERPORTAL_VENDOR $KBC_DEVELOPERPORTAL_APP)
   - docker push $REPOSITORY:test
-  - docker pull quay.io/keboola/syrup-cli:latest
 
 script:
-  - docker run --rm -e KBC_STORAGE_TOKEN quay.io/keboola/syrup-cli:latest run-job $KBC_DEVELOPERPORTAL_APP $KBC_APP_TEST_CONFIG test
+  - curl --location --request POST "https://queue.keboola.com/jobs" --header "X-StorageApi-Token:$KBC_STORAGE_TOKEN" --header "Content-Type:application/json" --data-raw '{"component":"'"$KBC_DEVELOPERPORTAL_APP"'","config":"'"$KBC_APP_TEST_CONFIG"'","tag":"test","mode":"run"}'
 
 after_success:
   - docker images
@@ -368,8 +367,7 @@ The commands above
 - tag the image as `test`.
 - get the command to login to the registry (`ecr:get-login`) and execute it (i.e., log in).
 - push the image to the registry.
-- pull the job runner CLI client ([Syrup PHP CLI](https://github.com/keboola/syrup-php-cli)).
-- run the specified test job on Keboola using the `/{component}/{config}/run/tag/{tag}` -- [Keboola Docker API](https://kebooladocker.docs.apiary.io/#reference/run/create-a-job-with-image/run-job). The tag used is `test`.
+- run the specified test job on Keboola using the [Queue API](https://app.swaggerhub.com/apis-docs/keboola/job-queue-api). The tag used is `test`.
 
 If you want to run multiple test jobs, simply repeat the command with the different configuration IDs
 that you would like to test.
diff --git a/extend/component/running/index.md b/extend/component/running/index.md
index 9ba6c997..222efb87 100644
--- a/extend/component/running/index.md
+++ b/extend/component/running/index.md
@@ -145,10 +145,9 @@ destination to which the table will be downloaded for the component; it will the
 
 The entire `configData.storage` node is generated by the UI. The node `parameters` contains arbitrary
 parameters which are passed to the component. The URL of the request
-is `https://syrup.keboola.com/docker/{{componentId}}/input` (in the [US Region](/overview/api/#regions-and-endpoints)).
-The request body is in JSON. Replace the `componentId` by the ID of the component for which you
-want to generate the config file (e.g., `keboola-test.ex-docs-tutorial`). Enter your Storage API token
-into **X-StorageAPI-Token** header and run the request.
+is `https://queue.keboola.com/jobs` (in the [US Region](/overview/api/#regions-and-endpoints)).
+
+The request is same to the one used when running a job.
 
 ### Running with Configuration
 In the [collection of sample requests](https://documenter.getpostman.com/view/3086797/kbc-samples/77h845D?version=latest#9b9f3e7b-de3b-4c90-bad6-a8760e3852eb),
@@ -182,7 +181,7 @@ When running the request with valid parameters, you should receive a response si
 {% highlight json %}
 {
     "id": "176883685",
-    "url": "https://syrup.keboola.com/queue/job/176883685",
+    "url": "https://queue.keboola.com/jobs/176883685",
     "status": "waiting"
 }
 {% endhighlight %}
diff --git a/extend/component/tutorial/debugging.md b/extend/component/tutorial/debugging.md
index 83fb00db..0be57c9f 100644
--- a/extend/component/tutorial/debugging.md
+++ b/extend/component/tutorial/debugging.md
@@ -195,11 +195,14 @@ tagged the release `0.0.7-test`, you can run the configuration `354678919` by is
 following API call:
 
     curl -X POST \
-    https://syrup.keboola.com/docker/keboola-test.ex-docs-tutorial/run/tag/0.0.7-test \
+    https://queue.keboola.com/jobs \
     -H 'Content-Type: application/json' \
     -H 'X-StorageApi-Token: your-token' \
     -d '{
-    "config": "354678919"
+    "component": "keboola-test.ex-docs-tutorial",
+    "config": "354678919",
+    "tag": "0.0.7-test",
+    "mode": "run"
     }'
 
 In the job detail -- under **Parameters & Results**, , you'll see that a specific tag was requested. In the job events, you can then