Skip to main content
Solved

V3 to V4 Migration - Replacement for /datasets/ reader/writer endpoint

  • April 13, 2026
  • 4 replies
  • 59 views
ecx
Supporter
Forum|alt.badge.img+6

Hi all,

I've been using the FME Flow REST API v3 for server metadata extraction and analysis, and one of the key endpoints I relied on was the datasets endpoint to extract reader/writer information from workspaces:

GET $(Environment_URL)/fmerest/v3/repositories/{repository}/items/{item}/datasets/source
GET $(Environment_URL)/fmerest/v3/repositories/{repository}/items/{item}/datasets/destination

This gave me a clean, simple output showing the format, location, and name of each reader/writer, exactly what I needed for server analysis and metadata:


With the v4 migration I can see this has been explicitly removed with no direct replacement:

Description V3 Endpoint Suggested Action
Get dataset information for a repository item /repositories/{repository}/items/{item}/datasets/* This functionality has been removed.

I've looked at reading the .fmw file directly using the FME Workspace Reader as an alternative, but the data is incomplete and doesn't come out in a clean usable format the way the old endpoint did.

Is there a v4 endpoint that provides equivalent reader/writer dataset information that I've missed? Or is there a recommended approach for getting this data cleanly in v4?

Thanks

Best answer by ebygomm

Have you looked at this API call

 

/fmeapiv4/workspaces/{repository}/{workspace}

 

Followed by a JSONFragmenter with the queries

json["datasets"]["source"][*]
json["datasets"]["destination"][*]

 

    4 replies

    ebygomm
    Influencer
    Forum|alt.badge.img+48
    • ebygommInfluencer
    • Influencer
    • Best Answer
    • April 13, 2026

    Have you looked at this API call

     

    /fmeapiv4/workspaces/{repository}/{workspace}

     

    Followed by a JSONFragmenter with the queries

    json["datasets"]["source"][*]
    json["datasets"]["destination"][*]

     

      ecx
      Supporter
      Forum|alt.badge.img+6
      • ecxSupporter
      • Author
      • Supporter
      • April 14, 2026

      Thanks @ebygomm, I’ll give that a go.

      When I navigate to my locally hosted fme api v4 documents (at $(Environment_URL)/fmeapiv4/docs/index.html#/) there actually isnt mention to /workspace/ endpoint! but when I use it as you suggested, I can reach that endpoint. 


      Interestingly I can’t seem to find online documentation for fme rest v4,
      I’ve found this page:
      https://docs.safe.com/fme/html/FME-Flow/DevelopersGuide/REST-API-Method-Reference.htm
      which links to:
      https://docs.safe.com/fme/html/FME_REST/apidoc/v4/index.html
      but returns in a 404

      I’m mostly mentioning this because someone from FME should possibly fix these 404’s and missing api endpoints in internal documentation.

      I am using:
      FME Flow 2026.1
      Build 26103 - win64

      ebygomm
      Influencer
      Forum|alt.badge.img+48
      • ebygommInfluencer
      • Influencer
      • April 15, 2026

      I’m trying to find the page where i found the detail. There was a line near the repository endpoint information that said calls that only applied to workspaces would now be done via the workspace endpoint, and that detail was lower down the page. I can’t find it now though!

       

      The line is in the locally hosted documentation but as you say, there isn’t a mention of the workspace endpoint but i must have found the detail somwhere...

      repositories

      The repositories API has been updated with a cleaner design for endpoint paths. Endpoints that apply to all types of repository items remain in the “/repositories/*” API. Endpoints that apply only to workspaces are moved to the “/workspaces/*” API.”

      ebygomm
      Influencer
      Forum|alt.badge.img+48
      • ebygommInfluencer
      • Influencer
      • April 15, 2026

      On the API endpoints page, it’s listed in the repository section

       

      Community Stats

      32,470
      Posts
      123,347
      Replies
      40,634
      Members
      Terms & ConditionsCookie settingsAccessibility statement
      A product of
      Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.