Scripted REST routes

A Scripted REST route is an inbound endpoint you define in WP-PFManagement — a namespace, version, HTTP method and path — that WordPress registers on your site and that runs a workflow (or returns entity data) when called. You configure the route in Management; the screenshots of that configuration live on the Management side.

The route

Routes register under /wp-json/{namespace}/{version}/{path} — the namespace defaults to pfw-scripted and is set per route in Management. Each route is keyed by its {namespace, version, method, path} so two versions can coexist.

Authentication

A scripted route requires an authenticated caller — an unauthenticated request is rejected with 401. Whatever the caller authenticated as (a WordPress user, an API key, an OAuth bearer) is the identity the route runs under, so the inherited moat applies to any records it touches. If WP-PFManagement is not active the route returns 503 rather than running unguarded.

Inputs become pins

The input fields you declare on the route in Management are projected into the workflow as typed pins — each declared field arrives as a discrete, typed input the graph can read. You wire the workflow against those pins; you never parse the raw request by hand.