Workflow API returns 'Workflow not found' for existing and newly-created backend workflows

Hey everyone, hoping someone’s run into this before. I’ve got the Workflow API enabled (Settings → API), and the root URL shows as https://creatorssociety.plus/version-test/api/1.1/wf. My Data API is working totally fine on this same domain — I can GET /obj/user and get real records back without any issue.

But no matter what backend workflow I try to call externally, I get back:

{"statusCode":404,"body":{"status":"NOT_FOUND","message":"Workflow not found [name]"}}

I even made a brand new, super simple test workflow just now — no parameters, one action, saved and everything — and it still comes back “not found” the second I try to hit it from outside. So it doesn’t seem to be about naming or anything specific to the workflows themselves.

I’ve tried both GET and POST, tried hitting it through my custom domain and also tried the version-test and live paths, and I’m passing a valid API token in the Authorization header each time. Nothing changes the result.

Any idea what would cause the Workflow API to just not “see” backend workflows that clearly exist and are saved in the editor? Feels like something isn’t registering on the routing side. Would appreciate any pointers before I open a support ticket.

Doesn’t seem to have a name. Maybe screenshot of your endpoint settings?

Is this what you’re looking for?

You didn’t set expose as a public API.

Thank you. That was it. silly me