Skip to main content
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
richanthony
New Contributor III

Passing Parameters to a fabric pipeline via the API

I have successfully call a data flow from power automate using an HTTP connector and this basic URL https://api.fabric.microsoft.com/v1/workspaces/@{variables('WorkspaceID')}/items/@{variables('Pipeli....

 

However this won't pass a parameter in to the pipeline which I need it to do, has anyone got any ideas on how to pass an parameter in to a dataflow via the API. the documenation is not great for this.

2 ACCEPTED SOLUTIONS
lbendlin
Esteemed Contributor III

You would use a POST call instead of a GET and specify your parameters in the body payload.

 

Job Scheduler - Run On Demand Item Job - REST API (Core) | Microsoft Learn

View solution in original post

richanthony
New Contributor III

I followed this link and found that the body I was using was not correct this format worked:

 

{
"executionData": {
"parameters": {
"Param1": "value1",
"Param2": 123,
"Param3": true
}
}
}

View solution in original post

3 REPLIES 3
lbendlin
Esteemed Contributor III

You would use a POST call instead of a GET and specify your parameters in the body payload.

 

Job Scheduler - Run On Demand Item Job - REST API (Core) | Microsoft Learn

As @lbendlin says, parameters should be able to be passed in throught the payload of the POST request.
Here's a Medium.com article on it - although I'm trying to use sempy_labs instead.
https://murggu.medium.com/fabric-rest-api-data-pipelines-33b1b987efcf

I am however getting a 404 back from the server and although the pipeline is triggering, it's not passing the parameter in.


FabricHTTPException: 404 Not Found for url: https://api.fabric.microsoft.com/v1/operations/<guid> Error: {"requestId":"<guid>","errorCode":"NotFound","message":"The endpoint or resource could not be found"}

 



richanthony
New Contributor III

I followed this link and found that the body I was using was not correct this format worked:

 

{
"executionData": {
"parameters": {
"Param1": "value1",
"Param2": 123,
"Param3": true
}
}
}

Helpful resources

Announcements
Users online (27)