Best Of

For anyone who has found this thread in the future (Like I just did),

You can use transient ids in the queryString, its just a small little change from what I was trying.

"queryString": "query = qTransient(\"JHD\");"

The other thing to note is that this only works on certain api versions, so doing /api/partstudios… might not work,
but /api/v6/partstudios does.

There isn't anything like a skTransform function (at least not one that's publically documented). When making sketches in FS, it's more important that you get your initial coordinate system correct, instead of creating a sketch somewhere and then moving it. That's part of the reason that the sketch documentation says constraints are mostly unnecessary when sketching in FS, you can usually pinpoint exactly where you want it with some good vector math. Another approach could be to sketch and extrude, then do the opTransform function (this depends on the use case of course).

If you want my advice though, I would recommend staying away from sketching in FS. What I do almost every time I need sketches generated by a custom feature is I make a part studio with that sketch in it, set it up with configuration parameters, then I just derive the sketch in using the custom feature and from there it's much easier to place/rotate the sketch entity. It's also way easier to edit that sketch since you can just edit it in a part studio instead of redoing your logic for constraints in FS.