---
title: "Connect module: widget"
description: What the widget module is, why it is always conformant in v1, and where a vendor's widget snippet comes from.
---

For the operator's engineer embedding a vendor's front-end widget.

# widget

Some vendors run part of their flow in the player's browser, for example a verification screen. The widget module covers embedding that front-end snippet in your site.

## Who calls whom

Nothing calls you and you call nothing for this module. The vendor's snippet runs in the player's browser on your page.

## Where the snippet comes from

When a Marketplace connector requires `widget`, `connect_connector_requirements` and `connect_activate` (and their REST twins under `/operators/me/connect/marketplace/`) return the vendor's snippet in a `snippets` array, with the language and the code. If the vendor has not published one yet, the response lists `widget` under `snippetsUnavailable` instead.

## Headers

None. Do not put an `oh_live_` key, a signing secret or a callback key in a browser snippet.

## How it becomes conformant

In v1 the widget module is constant: it is always `conformant`, because there is nothing on your side to test until you embed the vendor's snippet. Its `evidence` is always `derived`, so `connect_status` never presents it as proven by a run.

## Conformance

None in v1.

## Samples

There is no Connect sample. The vendor's snippet is the code to embed.