Start a pathway execution
Creates a channel-agnostic pathway execution and returns both the lifecycle envelope and the first node to render. The server resolves the operating organisation from the supplied coordinates, pins the execution to the current active pathway version, and flattens prompt and option text against the requested locale. The same shape serves mobile, web, voice, and call-centre channels; renderers map kind, prompt, and options onto channel-native UI. The first node is delivered inline so the client never needs a second round-trip to start rendering. Subsequent calls advance the execution via submitAnswer, then call complete or abandon.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Request
Latitude at execution start (WGS84). Used by the server to resolve the operating organisation and jurisdiction.
Longitude at execution start (WGS84). See latitude for resolution notes.
Calling device platform. Used by mobile and web channels for analytics. Optional on voice and call-centre.
GPS accuracy in metres. Used to flag low-confidence boundary attributions in analytics.
Response
Lifecycle envelope for the newly-started execution.
First node to render. Saves a second round-trip on start; the client can render immediately from this payload.