Forum Discussion
REST API for third party workload items
Currently you won't be able to create REST API for 3rd party workloads. With the release of the Fabric extensibility toolkit we are about to release very soon the ability for Workload Developers declare their item definition and than you will be able to create 3rd party workload items.
The Fabric workload development a create item API is only for the workload developer itself to for using workloads programatically.
Thanks for asking!
As far as I know, there is no public REST API available. But I can propose the workaround below.
“Create item” in Fabric only works for the built-in item types Microsoft lists. Third-party workload item types are not exposed through that endpoint. Those items are provisioned by Fabric on behalf of the workload; using internal calls, the workload registers during onboarding.
What you can do
If you are the workload vendor, you need the Fabric Workload Development onboarding path. Your service provisions items through the internal bridge, not through the public REST surface.
If you are a customer using a third-party workload, ask the vendor. Some vendors expose their own API or UI action that triggers provisioning inside Fabric. There is no tenant-side REST you can call yourself.
For automation, stick to what is supported: service principals, Items REST for native types, Git integration, or Deployment pipelines for native artifacts. Third-party items usually do not support Git yet.
Practical next steps
• Check the supported itemTypes list in the Items REST docs. If your third-party type is not listed, you will not create it via REST.
• Ask the workload vendor for a “create/provision” API or FAB action.
• If you own the workload, request Microsoft’s partner docs for the workload bridge and item registration.
Thank you!
Did I answer your question? Mark my post as a solution!
Understood. I'm a workload vendor and have set up the Fabric Workload Development environment. My understanding was that we could only trigger item creator using the JavaScript API within our iFrame according to the documentation here. Could you elaborate on how the service can provision an item through this "internal bridge"? Is there a way to start the item creation flow without using the UI?