LedgerSync-hosted MX Connect wrapper page (browser-facing)
Browser-facing HTML page — not an integrator API call. When a
connection routes to MX, the widget_url action returned by
POST /clients/{client_id}/connections points here (MX Connect
has no native post-Connect redirect of its own). Open it in the
user’s browser or iframe it, exactly like Finicity Connect.
The page verifies the short-lived wrapper token, embeds the MX
Connect widget, and when the user finishes linking either
redirects its own window to your registered redirect_url with
an ls_token query parameter — the same contract as the
Finicity flow, verified at
POST /connections/redirect-token/verify — or shows a
“Connected” end state when no redirect_url was supplied at
initiate time.
No API key is required: the HS256 wrapper token in the query
string is the capability. Tampered, expired, or missing tokens
render a static error page (text/html, not the JSON error
envelope).
Query Parameters
HS256 wrapper token minted when the MX connection was
initiated. Re-renderable within its 30-minute TTL (browser
refresh mid-flow is safe); the embedded ls_token stays
strictly single-use at verify time.
Response
The wrapper page.
The response is of type string.