[garethx]

Replaces what look like real people's details and tokens in 104 sample payloads across 17 providers published to samples.hookdeck.com. Only the values change: every JSON key and its order is the same, the diff is 206 lines replaced one for one, and the JSON formatting is untouched. yarn compile succeeds and yarn test passes 26 of 26.

No real values appear in this PR text or the commit message.

What was replaced

Data	Replacement
Emails	user1@example.com, user2@example.com (whichever wasn't already used for another person in the same file)
Names and usernames	Jane Doe, Jane, Example User, example_user, Example Company, EXAMPLE COMPANY, INC.
Addresses	1 Example Street, 2 Example Street (where a file has two), Suite 100, Example City, XX codes, zeroed postcodes
Date of birth	1990-01-01
Token-bearing URLs	Same host and path shape, with example-token in place of the token, and example.com for a third-party request-bin host
Plain tokens, account numbers and filing numbers	Same length and prefix, with exampleToken and zeros

Files and fields

Provider	Files	Fields
azure-devops	6	git.repo.created, git.repo.forked, tfvc.checkin, release-created, deployment-started, deployment-approval-completed: every displayName (author, checkedInBy, createdBy, modifiedBy, owner, approver, initiatedBy) and the same names inside message and detailedMessage text, html and markdown
bird	1	whatsapp.received: data.from.display_name, data.from.username
boldsign	7	signerDetail.signerName in the three IdentityVerification* events, senderDetail.name in IdentityVerificationFailed, and senderDetail.emailAddress in IdentityVerificationFailed, SignerSaved, SendFailed, TemplateSendFailed and TemplateCreateFailed
check	3	bank_account.created: plaid_public_token. federal_ein_verification.created: federal_ein. workplace.created: address.line1, city, state, postal_code
coterie	1	applications: ContactFirstName, ContactLastName, MailingAddress*, Locations[0] street/city/state/zip, AdditionalInsureds[0] street/city/state/zip and FullAddress
documenso	4	DOCUMENT_CREATED, SENT, COMPLETED, CANCELLED: recipient token in recipients[] and Recipient[]. Each distinct token got its own placeholder, so matching tokens still match
doordash-drive	1	DASHER_DROPPED_OFF: pickup_address, dropoff_address, tracking_url
fourkites	1	LOAD_CREATION: EncryptedAccessToken, EncryptedUrl
go1	1	3.0.0/enrollment.complete: body.url
honeybadger	11	actor.name, project.users[].name and the same name in message; actor.email, project.owner.email, project.users[].email and deploy.local_username where they carried that person's address. Covers commented, assigned, deployed, down, up, check_in_missing, check_in_reporting, volume_spike, rate_exceeded, plus resolved and unresolved, which repeat the same address
jfrog	9	app_trust.application_{creation,update,deletion}_{started,completed,failed}: the username in source
kombo	1	assessment.order-received: job.location.street_1
lokalise	19	user.email, the same address in every file
middesk	5	lien.{found,terminated,continued,lapsed}: debtors[0].name, debtors[0].addresses[0].full_address, file_number. run.interrupted: the address in artifacts[0].title and summary
nium	32	name, merchantName, beneficiaryName, remitterName, remitter.dob, remitterAccountNumber, virtualAccountNumber
oncehub	1	v2/booking.scheduled: data.owner.first_name, data.owner.email, booking_calendar.name, booking_calendar.subject, booking_calendar.url
onelogin	1	5: user_name, actor_user_name

Worth a look

• nium: 6 of the 38 flagged files are unchanged. CARD_EXPIRY_CARD, CARD_UNBLOCK_PIN and four REMIT_TRANSACTION_* events only hold stock placeholder names and already-masked card and account numbers. Stock placeholder names in the other nium files were kept too, as were bank names, routing codes, masked numbers and nium's own reference ids.
• Already-placeholder values kept: the doordash-drive contact and dasher names, the documenso recipient names, the kombo zip and city, a cartoon character's name in honeybadger, and boldsign's generic Sender/Signer names.
• middesk: the debtor is a business, but its name, address and state filing number together identify a real lien record, so all three were replaced. The secured party, a filing-service company, is kept.
• honeybadger IPs: the forwarded-for IPs were already in the 203.0.113.x range. REMOTE_ADDR in rate_exceeded is a private 10.x address and was kept. The fault message in commented and assigned contains a third-party spam handle as part of the captured error text; it was left as it is.
• jfrog: jpd_origin names a JFrog event instance rather than a person and was kept.

Checks

• All 104 changed files parse as JSON. A walk of each file against main shows the same keys, key order, array lengths and value types, with only the intended values different, and each file's diff has as many removed lines as added.
• A search of the changed files finds none of the old values. Short values (first names, state codes, postcodes) were compared field by field.
• A search of the rest of the repo finds none of the old values, except one city name, one state code and the word used as a last name, which appear as ordinary values in unrelated providers' samples and were left alone.
• yarn compile succeeds and yarn test passes 26 of 26.

Git history: not rewritten

The old values stay in public git history, as with #82 and #83. This PR doesn't change that.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
webhook-samples	Ready	Preview	Nov 10, 2026 5:30pm UTC