From 43aab30004a0acce310efd5a887cac951741d3d5 Mon Sep 17 00:00:00 2001
From: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com>
Date: Thu, 8 Aug 2024 09:50:38 +0200
Subject: [PATCH] docs(cli): Document `send-event` format (#10995)

Link to the [Event Payloads](https://develop.sentry.dev/sdk/event-payloads/) page from the `send-event` command page, so that users know what format their event should follow.

Closes https://github.com/getsentry/sentry-docs/issues/9538
---
 docs/cli/send-event.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/cli/send-event.mdx b/docs/cli/send-event.mdx
index 4398dcd9518e5..47ef0b4f1d0ca 100644
--- a/docs/cli/send-event.mdx
+++ b/docs/cli/send-event.mdx
@@ -70,7 +70,7 @@ sentry-cli send-event -m "a failure" -t task:create-user
 
 ## Stored Events
 
-As of version `1.71`, the `send-event` command can accept an optional argument that specifies a path to the stored JSON representation of an event. When used, it will load the file, validate the event and send it to Sentry.
+As of version `1.71`, the `send-event` command can accept an optional argument that specifies a path to the stored JSON representation of an [event payload](https://develop.sentry.dev/sdk/event-payloads/). When used, it will load the file, validate the event and send it to Sentry.
 
 ```bash
 sentry-cli send-event ./events/20211029150006.json