> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sequenzy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Received Event Sample

> Reuse the latest recorded event payload when testing a sequence

Read the latest retained event with an exact name in your selected workspace. This includes custom events and older history, across all subscribers. There is no additional recent-only cutoff. The response does not record an event, enroll a subscriber or send an email. You need `subscribers:read`; read-only workspace members can use this lookup.

<ParamField query="eventName" type="string" required>
  Exact recorded event name. Surrounding whitespace is trimmed. No alias
  resolution or published schema lookup is performed.
</ParamField>

<ResponseField name="eventName" type="string" required>
  The trimmed event name.
</ResponseField>

<ResponseField name="sample" type="object | null" required>
  Latest retained occurrence, or null when none exists. Contains `eventTime`
  (UTC timestamp), `subscriberId` (the source subscriber ID) and `properties` (a
  JSON object, preserving arrays, nested objects and null values). Empty
  properties remain an empty object. Equally recent events have no guaranteed
  tie order.
</ResponseField>

Copy `sample.properties` into the `customVariables` object for [Start Sequence Test Run](/api-reference/sequences/test-run). Review or edit the data first. The source subscriber may differ from your test recipient; copying the properties does not change that recipient. A read can be retried safely. An analytics failure returns an error, never a fabricated empty sample.

```bash theme={null}
sequenzy events sample ecommerce.checkout_started --company company_123 --json
```

With MCP, use `get_event_sample` with `eventName` and optional `companyId`, then pass the returned properties to `start_sequence_test_run`. To clear copied data, omit `customVariables` or supply `{}` on your next test. In the dashboard, clear the text field.

## Errors

* **400**: Missing or blank event name, or missing company selection for a personal key.
* **401**: Missing or invalid authentication.
* **403**: Missing `subscribers:read` or access to the requested company.
* **500**: Analytics lookup failed. Retry the read; no test run was started.

No matching event is a successful **200** response with `sample: null`, not a 404.