diff --git a/content/en/docs/deployment/general/mendix-pipelines.md b/content/en/docs/deployment/general/mendix-pipelines.md
index aa8602fe189..7340e8f2eb5 100644
--- a/content/en/docs/deployment/general/mendix-pipelines.md
+++ b/content/en/docs/deployment/general/mendix-pipelines.md
@@ -167,6 +167,27 @@ Check out a branch. To configure this step, use the drop-down menu to select the
 
 Build a deployment package based on the latest major, minor, or patch version of the branch you checked out. The highest version is incremented based on the increment settings specified in this step.
 
+##### GET Request
+
+Retrieve information from an external API to inform or control the pipeline's next steps. The GET request step requires the following:
+
+* **Request URL** – The endpoint to query.
+* **Initial delay (seconds)** – Time to wait before the first request. Must be between 0 and 10800 seconds.
+* **Polling interval (seconds)** – Time between retries. Must be between 5 and 300 seconds.
+* **Maximum wait time (seconds)** – Total time to wait before timing out. Must be between 0 and 10800 seconds.
+
+The GET request step has the following [success criteria](https://jqlang.org/manuallets):
+
+* **API call succeeds** – The API returns a 2xx response.
+* **API output meets condition** – The user-defined condition in jQuery  evaluates to true (for example, `.Result = Success`).
+
+##### POST Request
+
+Send structured data to an external API to trigger an action or update a system. The POST request step requires the **Request URL**, which is the endpoint to send data to. The [success criteria](https://jqlang.org/manuallets) for the POST request step are:
+
+* **API call succeeds** – The API returns a 2xx response.
+* **API output meets condition** – The user-defined condition in jQuery evaluates to true (for example, `.Result = Success`).
+
 ##### Maia Best Practice Recommender{##recommender}
 
 Evaluate the results of the [Maia Best Practice Recommender](/refguide/best-practice-recommender/) within your Mendix Pipeline. You can configure this step to fail the Mendix Pipeline if errors, warnings, deprecations, and/or recommendations are detected.
diff --git a/content/en/docs/releasenotes/deployment/mendix-pipelines.md b/content/en/docs/releasenotes/deployment/mendix-pipelines.md
index 4434be9013e..75de74c5a29 100644
--- a/content/en/docs/releasenotes/deployment/mendix-pipelines.md
+++ b/content/en/docs/releasenotes/deployment/mendix-pipelines.md
@@ -12,6 +12,12 @@ To see the current status of the Mendix Pipelines, see [Mendix Status](https://s
 
 ## 2026
 
+### March 12, 2026
+
+#### New Features
+
+* We have added two new steps, [GET request](/developerportal/deploy/mendix-pipelines/#get-request) and [POST request](/developerportal/deploy/mendix-pipelines/#post-request), to Mendix Pipelines. These new steps allow Mendix Pipelines to retrieve and send structured data to external APIs.
+
 ### February 26, 2026
 
 #### New Features