Connector documentation

Start a tracked journey into Westland Express’s existing tenant quote and payment flow. This connector records handoffs and browser observations; it does not create quotes, charge cards, or bind policies.

OpenAPI specification · Full agent guide

Connect Muse

Connection	Raw API
Base URL	See the OpenAPI server URL
Specification	/openapi.json
Authentication	X-API-Key, plus X-Journey-Token for private journey operations

Start after consent

POST /v1/journeys
X-API-Key: <connector key>
Idempotency-Key: <unique request ID>
Content-Type: application/json

{"product":"tenant_insurance","language":"en","mode":"assisted","campaign":"muse","analytics_consent":true}

Keep the returned journey_token in secure tool context. Open handoff_url in the customer’s authorized browser session. Reuse the same idempotency key when retrying a request.

Report only observed steps

POST /v1/journeys/{journey_id}/observations with both headers. Read GET /v1/journeys/{journey_id} for status. Event IDs deduplicate retries; reusing an ID with different content returns 409.

{"event_id":"<unique event ID>","type":"stage_viewed","stage":"name","evidence":"active_step_visible","observed_at":"<ISO 8601 timestamp with timezone>"}

Access requirements

A ExpressTrack-issued connector key and customer consent are required. Journeys expire after 30 days. English flow only. Westland determines eligibility and supported regions. Muse needs browser interaction and permission to report observed progress. Without browser observations, progress after handoff is unknown.

Rate limits: 120 connector requests per minute per key; 60 handoff requests per minute per link. Responses use 429 when limited. A journey accepts up to 500 events. Never send names, addresses, answers, screenshots, passwords, card numbers, payment tokens or raw page text.

Checkout and evidence

Payment stays in Westland. A card linked to Muse is usable only through a supported secure wallet flow; otherwise the customer completes payment directly. Never copy wallet secrets into this connector. Report payment success and policy issuance separately. After an observed success, inspect the existing transaction before retrying.

Handoff activations measure submitted continue actions, not verified human clicks. Browser reports are labelled agent_reported. Missing events do not establish abandonment, and observed issuance does not establish provider-verified conversion or commission.

Privacy and operations

Only random journey IDs and categorical progress events are stored. Authenticated dashboard access is separate from connector credentials. No personal application answers or payment data are requested. Configure referral attribution only with a real Westland-issued code. Data cleanup must be performed by an authorized operator; automatic retention deletion is not yet enabled.