Data Pipeline API - how to get the parameters of an executed pipeline?

[dafad_dew]

Hi...

Trying to work out if it's possible to get the parameters a data pipeline was executed with.

Looks like the API supports executing a pipeline with parameters: REST API - Run on-demand item job

And it also supports Getting the job instance by ID: REST API - Get item job instance

But I can't find any API which provides the parameters that were provided to run a job instance.

A GET to workspaces/{workspace id}/items/{pipeline id}/jobs/instances/{job id} does not include the parameters. Sample response is:

{ 
   "id": "{job id}",
   "itemId": "{pipeline id}",
   "jobType": "Pipeline",
   "invokeType": "Manual",
   "status": "InProgress",
   "failureReason": null,
   "rootActivityId": "{id}",
   "startTimeUtc": "2025-05-27T07:44:55.78Z",
   "endTimeUtc": null,
   "ResponseHeaders": {
      <snip>
   },
   "executionDuration": 0
}

No parameters 😞

The parameters are available in the Fabric workspace via the Monitoring Hub - click on a pipeline run, and a box appears with the number of parameters over on the right hand side:

click on the number, and the parameter names and values appear.

So how do I get that same list of parameter names and values via the Fabric API?

Thanks!

DD.

[v-ssriganesh]

Hi @dafad_dew,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.

[v-ssriganesh]

Hi @dafad_dew,

May I ask if you have resolved this issue? If so, please mark it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-ssriganesh · Accepted solution]

Hi @dafad_dew,
Thank you for reaching out to the Microsoft Fabric Community Forum.

You're right while the Monitoring Hub UI in Microsoft Fabric shows the number and details of parameters used during a pipeline run, the current REST APIs do not expose these parameters via the available job instance endpoints.

Here are two possible approaches:

• Use a Notebook or Data Flow activity to write pipeline().parameters to a Lakehouse or file for future tracking.
• If triggering the pipeline via the Run on-demand item job API, log the jobId and parameters in your external system for traceability.

I encourage you to submit this as a feature request on the Microsoft Fabric Ideas Forum: Fabric Ideas - Microsoft Fabric Community The microsoft team actively reviews ideas with strong community support, and your suggestion could help prioritize this enhancement for a future update.

If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.

[v-ssriganesh]

Hi @dafad_dew,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please accept it as a solution and give it a 'Kudos' so other community members with similar problems can find a solution faster.
Thank you.