Forum Discussion
Pipeline Trigger using API
Hi RajPunjabi ,
Thanks for the update! I understand that the "Invalid jobType" error is persisting. Since you’re scheduling the pipeline manually for now.
A few things to check: Ensure that jobType is not included in the request URL, as the API automatically determines it. Also, verify that your {pipelineId} is correct and matches an existing pipeline in your Fabric workspace. Additionally, double-check that your access token has the required permissions (Pipeline Operator or Fabric Admin).
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thankyou.
Hi RajPunjabi ,
Thank you for posting in the Microsoft Fabric Community.
The "InvalidJobType" error occurs because jobType=Pipeline is not the correct value for triggering a pipeline in Microsoft Fabric.
Try using the correct API call:
Authorization: Bearer {accessToken}
Content-Type: application/json
Request Body:
{
"executionData": {
"parameters": {}
}
}
Please ensure that {pipelineId} is a valid pipeline ID from your Fabric workspace. You can verify this in the Fabric UI. Also, confirm that your API token has sufficient permissions (Fabric Admin or Pipeline Operator role).
If the error persists, you can manually trigger the pipeline from the Microsoft Fabric UI as a temporary solution.
I hope this will resolve your issue, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thankyou.
Still it is giving as Invalid jobtype. I will schedule that manually for now
Hi RajPunjabi ,
Thanks for the update! I understand that the "Invalid jobType" error is persisting. Since you’re scheduling the pipeline manually for now.
A few things to check: Ensure that jobType is not included in the request URL, as the API automatically determines it. Also, verify that your {pipelineId} is correct and matches an existing pipeline in your Fabric workspace. Additionally, double-check that your access token has the required permissions (Pipeline Operator or Fabric Admin).
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thankyou.
Hi @RajPunjabi ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
