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

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
mprewett
Regular Visitor

Fabric data pipeline public REST API Query Activity Runs

I am using Postman to call the the Fabric data pipeline public REST API's to query activity runs. I keep getting an empty result set when calling the queryactivityruns api using the pipeline job instance id, but the "Get item job instance" api returns correct results using the same job instance ID. Are these different ID's?

 

This returns the correct job instance (GET):

 

--header 'content-type: application/json' \
--header 'Authorization: ••••••' \
--data '{
}'

 

This returns an empty result set (POST):

 

--header 'content-type: application/json' \
--header 'Authorization: ••••••' \
--data '{
}'
 
@kromerm, adding you for possible assistance since i saw you as a contributor for these API's. 
2 ACCEPTED SOLUTIONS
Anonymous
Not applicable

Hi @mprewett ,

It sounds like you're encountering an issue with the IDs used in your API calls. The job_instance_id used in the queryactivityruns API might be different from the one used in the Get item job instance API.

 

Here are a few things to check:

 

1. Ensure that the job_instance_id you are using in both API calls is exactly the same. Sometimes, there might be a slight difference or typo that could cause the issue.

 

2. Check the response data from the Get item job instance API to see if it includes any other IDs or references that might be needed for the queryactivityruns API.

 

3. Ensure that your API token has the necessary permissions to access both endpoints. Sometimes, different endpoints might require different scopes or permissions.

 

 

Best Regards

Yilong Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

larsaia
Regular Visitor

You need to provide something in the body, at least:

{"lastUpdatedAfter":"2025-06-11T08:55:57.7992493Z","lastUpdatedBefore":"2025-06-12T08:55:57.7992676Z"}

 

Its very difficult to find in the documentation: Fabric data pipeline public REST API - Microsoft Fabric | Microsoft Learn

I found a link to a similar question: How to use pagination in Azure Data factory with REST API - Microsoft Q&A 

 

There is some additional info in the DataFactory documentation, where some things seem to be applicable to fabric: Activity Runs - Query By Pipeline Run - REST API (Azure Data Factory) | Microsoft Learn

View solution in original post

4 REPLIES 4
larsaia
Regular Visitor

You need to provide something in the body, at least:

{"lastUpdatedAfter":"2025-06-11T08:55:57.7992493Z","lastUpdatedBefore":"2025-06-12T08:55:57.7992676Z"}

 

Its very difficult to find in the documentation: Fabric data pipeline public REST API - Microsoft Fabric | Microsoft Learn

I found a link to a similar question: How to use pagination in Azure Data factory with REST API - Microsoft Q&A 

 

There is some additional info in the DataFactory documentation, where some things seem to be applicable to fabric: Activity Runs - Query By Pipeline Run - REST API (Azure Data Factory) | Microsoft Learn

Thank you! Finding documentation on this was not easy.

I stumbled over your question, while searching for a solution, to use paging for this endpoint. The Fabric documentation is incorrect. I made it work, with the help from the Data Factory documentation. The last issue is, that I'm unable to change the pagesize.

Anonymous
Not applicable

Hi @mprewett ,

It sounds like you're encountering an issue with the IDs used in your API calls. The job_instance_id used in the queryactivityruns API might be different from the one used in the Get item job instance API.

 

Here are a few things to check:

 

1. Ensure that the job_instance_id you are using in both API calls is exactly the same. Sometimes, there might be a slight difference or typo that could cause the issue.

 

2. Check the response data from the Get item job instance API to see if it includes any other IDs or references that might be needed for the queryactivityruns API.

 

3. Ensure that your API token has the necessary permissions to access both endpoints. Sometimes, different endpoints might require different scopes or permissions.

 

 

Best Regards

Yilong Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

Find out what's new and trending in the Fabric community.

June FBC25 Carousel

Fabric Monthly Update - June 2025

Check out the June 2025 Fabric update to learn about new features.

Top Solution Authors