Setyenv · Docs
  • English
  • Spanish
  • Chinese
  • Japanese
  • Arabic
  • German
  • French
  • Hindi
  • Indonesian
  • Italian
  • Dutch
  • Portuguese
  • Russian
  • Turkish

Scripted REST

A Scripted REST route is a custom inbound endpoint you define in Management — a namespace, version, HTTP method and path (together its immutable identity) — that WordPress registers on your site. You give it either a direct EQL query or a workflow to run, and the input/output fields that become the route's typed pins.

The Scripted REST route editor — route identity, definition, query and input/output fields

The route always runs under the caller's own identity, so the inherited moat (row visibility, field projection, verb guard) applies to any records it touches. An unauthenticated request is rejected; if Management is not active the route returns 503 rather than running unguarded. The input fields you declare become the route's typed pins — you wire the workflow against those, never the raw request. See the run side at Scripted REST routes.