> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.benchling.com/in-vivo/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.benchling.com/in-vivo/_mcp/server.

# Sample type updated

POST 

Sent once per sample type updated. The payload is the sample type as updated.

Reference: https://docs.benchling.com/in-vivo/webhooks/webhook-team-glossary-sample-updated

## Request

### Headers

- `Signature` (string, required) — Lowercase hex-encoded HMAC-SHA256 of the raw request body, keyed with your webhook's signing secret. Compute it over the bytes exactly as received, before parsing, and compare in constant time.

### Payload

- `id` (string, required) — Unique identifier for a webhook event. A retried delivery carries the same identifier, so use it to discard duplicates.
- `event` (enum, required) — The event that occurred.
  - Allowed values: `team.glossary_sample.created`, `team.glossary_sample.updated`, `team.glossary_sample.deleted`
- `version` (enum, required) — A released version of the public API. Each OAuth client is registered against one version, which determines the response shape it receives.
  - Allowed values: `2022-12-14`
- `created_at` (datetime, required) — UTC timestamp with microsecond precision, always suffixed with `Z`, in the form `yyyy-MM-ddTHH:mm:ss.SSSSSSZ`.
- `payload` (TeamSampleGlossaryV1, required) — A sample type in your team's glossary.
- `client_id` (string, optional) — The OAuth client whose API request caused the event. Omitted when the event did not originate from an API request, and on events that never carry it.

## Types

### TeamSampleGlossaryV1

A sample type in your team's glossary.

- `id` (string, required) — Unique identifier for an entry in your team's own glossary.
- `title` (string, required) — The title of the sample type.
- `label` (string, required, nullable) — A short label for the sample type.
- `description` (string, required, nullable) — A longer description of the sample type.
- `status` (enum, required) — Whether a team glossary entry is available for use or archived.
  - Allowed values: `active`, `archived`
- `details` (list of string, required, nullable) — The details to record when a sample of this type is collected. Null when none are configured. Entries created through this API are always one of `weight`, `volume`, `width`, `length` or `depth`, but entries configured in the In Vivo app are not restricted to those values.