Hello Eric! first of thanks so much for this info. I was able to get the project level execution done from airflow and it worked as expected. I am in the process of doing CICD migration using the API credentials to the project using python SDK for streamsets and so far it is going as expected. I think for now, i am all set, but will reach out to you all in case i am stuck in any place.
Original Message:
Sent: 08/13/26 11:20 AM
From: Eric Greisdorf
Subject: streamsets project job instance to be run using API credential on fabric airflow
Hi Vivek,
I've created a little working example, and am able to reproduce the message by omitting the Project ID from the REST API.
I didn't have to recreate my API credentials, they're supplied like in this GitHub integration subscription video. [link]
The first Stage queries for Project Level Jobs tagged (example for a specific cost center), we Pivot the query results, then Start the Jobs.
Job Query: https://dev.hub.streamsets.com/jobrunner/rest/v1/saql/jobs/search?search=tag=in=mycostcenter&project=d57548e0-fd03-4352-8706-f6055a8271a5
Job Start: https://dev.hub.streamsets.com/jobrunner/rest/v1/job/e9f0d36c-d679-4b5d-9924-7612f4fbf6f0:d47ddc08-9b6a-11ed-a52e-df3027e96134/start?project=d57548e0-fd03-4352-8706-f6055a8271a5
The Project ID can be found under Manage Projects.
The Job ID can be found under 'Show Additional Info" for the Job.
Example Pipeline Job Being Started:
I hope this helps. Please reach out if we can be of further assistance.
Best Regards,
Eric
------------------------------
Eric Greisdorf
------------------------------
Original Message:
Sent: 08/12/26 06:34 PM
From: vivek thulasi
Subject: streamsets project job instance to be run using API credential on fabric airflow
Hello Eric!
Thank you for responding. The question i have with respect to your suggestion is on
"It's also been suggested you might be making an ORG level request to run a Project level resource and using "/jobrunner/rest/v1/jobs?project=14549ccc-..." should work."
The end of the line says, the above jobrunner script should work for the project if i am understanding it correctly. But the issue is, i am still facing error, this time it is
{ "ISSUES": [ { "code": "RESTAPI_08", "message": "ORG cannot perform actions on the object owned by Project Id 14549ccc-05de-437d-a4fa-ca7758ee50c8." } ]}
i have added the user to the job instance with read/write permissions. The user has been added to the project/ deployment engines/job instance(with read/write permissions)/pipeline(with read/write permissions). Hence i am not sure what else would need to be done. My only guess is how the API credentials are being created. Is there a process to see if it can be created at project level.
THanks
Vivek TP
------------------------------
vivek thulasi
------------------------------
Original Message:
Sent: 08/10/26 05:10 PM
From: Eric Greisdorf
Subject: streamsets project job instance to be run using API credential on fabric airflow
Hi Vivek,
Thank you for posting. I'm so glad to hear you're leveraging IBM StreamSets popular Projects capability.
I would suggest checking that your Service Account API credentials have the required role based access to the StreamSets Project, as described in the StreamSets Python SDK documentation [link].
It's also been suggested you might be making an ORG level request to run a Project level resource and using "/jobrunner/rest/v1/jobs?project=14549ccc-..." should work.
More information about defining Projects and User Roles can be found in the IBM StreamSets documentation. [link]
If the problem persists, please open a support case for tracking to the fastest resolution [link].
Best Regards,
Eric
------------------------------
Eric Greisdorf
------------------------------