Skip to main content
Dump the full registrant list for one event as CSV. The command writes directly to stdout and ignores --format / --json. Export is always CSV, by design, so it can be redirected straight to a file or piped into another tool.

​
Synopsis

talkvalue path event person export <eventId> > registrants.csv

​
Arguments

ArgumentTypeDescription
<eventId>integerEvent ID. Use event list to find one.

​
Options

This command takes no flags beyond the global flags. Passing --json or --format json prints a warning to stderr and still emits CSV.

​
Examples

​
1. Save to a file

talkvalue path event person export 18 > spring-summit.csv
Writes the CSV to spring-summit.csv. The header row is always present. Column order matches the dashboard registrant export.

​
2. Pipe into a transformer

talkvalue path event person export 18 \
  | csvtk grep -f primaryEmail -p "@acme.com$" \
  > spring-summit-acme.csv
Streams the CSV through csvtk (or mlr, xsv, etc.) without ever touching disk. Useful when the registrant list is large enough that round-tripping JSON would be expensive.

​
3. Snapshot for handoff

ts=$(date +%Y-%m-%d)
talkvalue path event person export 18 > "snapshots/event-18-$ts.csv"
Drop into a cron job or CI workflow for a periodic backup outside of TalkValue. Pair with the matching event ID in your file name so you can correlate snapshots over time.

​
Response

id,name,primaryEmail,primaryPhone,company,jobTitle,joinedAt,createdAt
142,"Alice Kim",alice@acme.com,+1-415-555-0199,"Acme Inc.","Head of Growth",2026-05-02T17:00:00Z,2026-04-12T00:00:00Z
…
The exact column set comes from the server and matches the dashboard CSV export. Treat the first row as the header and parse the rest as data.

​
See also