CRM WebHook

The MyRegistry Webhook allows you to receive real-time notifications whenever a new registrant signs up

Setup Requirements

  • Provide a Webhook Listener URL
  • Ensure your listener accepts POST requests with JSON payloads
  • Secure your endpoint with HTTPS and token validation

Integration Details

To enable MyRegistry CRM integration with Webhook, partners must: Set Up a WebHook Listener

FieldValue
FormatJSON payload (POST)
DeliveryReal-time (near instant)
RetriesFailed deliveries are retried automatically
Topic(s)
  • Registry.Signup
  • Registry.Update`

Message Structure

For Signup's (http body/json), each event contains two parts:

  1. Metadata: information about the event (ID, timestamp, type, version)
NameTypeDescription
eventIdStringIdentification of the Event (Internal Usage)
eventTimeDateTimeEvent Date and Time (UTC)
topicStringType of Messages:
  • “Registry.Signup” - A registry signed up to a merchant page
  • “Registry.Update” - A registry complete the signup or updates the registry
dataVersionStringData version of the message
payLoadRegistryDataRegistry Data for the Signup in JSON format
  1. Payload: detailed registry data and address data for the signup
Registry Data
NameTypeDescription
userIdIntegerUser Identification (MyRegistry Internal ID)
registryIdIntegerRegistry Identification (MyRegistry Internal ID)
firstNameStringRegistrant First Name
lastNameStringRegistrant Last Name
firstName2StringCo-Registrant First Name
lastName2StringCo-Registrant Last Name
registryTitleStringRegistry Title
emailStringEmail address
registryTypeIntegerThe registrant's registry type
- Wedding
- Baby
- Gift List
- Organization
wishListTypeStringSub-Type of Gift List
eventDateDateTimeEvent Date (UTC)
signupDateDateTimeSignup Date (UTC)
phoneStringPhone Number
mainAddressAddressDataMain Address
shippingAddressAddressDataShipping Address
storeIdStringPartner’s StoreId associated with the Registry at Signup.
Only present if signup happened on a Kiosk
signupCultureCodeStringLanguage code at signup (ISO-639 + ISO-3166)
registryUrlStringURL link to registry
merchantRegistryUrlStringMerchant URL link to registry
userWebsitesWebsiteDataList of websites with relation type:
- SignupOrigin
- SignupRelated
- AssociatedPartner

Address Data
NameTypeDescription
street1StringAddress Street
street2StringAddress Street 2
cityStringAddress City
stateStringAddress State
zipCodeStringAddress ZipCode
countryCodeStringAddress Country code (ISO 3166-1 alpha-2 code)


Example Payload

Below is a sample Registry.Signup event delivered to webhook endpoint:

{
	"payLoad": {
    	"userId": 12639,
    	"registryId": 12621,
    	"firstName": "Test",
    	"lastName": "Subject",
    	"firstName2": "Second",
    	"lastName2": "Name",
    	"registryTitle": null,
    	"email": "[email protected]",
    	"registryType": 1,
    	"wishListType": "Housewarming",
    	"eventDate": "2024-10-31T04:00:00Z",
    	"signupDate": "2024-10-23T21:01:17.42Z",
    	"phone": "(202) 222-1234",
    	"mainAddress": {
        	"street1": "",
        	"street2": "",
        	"city": "Iselin",
        	"state": "NJ",
        	"zipCode": "",
        	"countryCode": "US"
    	},
    	"shippingAddress": {
        	"street1": "1234 Unicorn Parkway",
        	"street2": "",
        	"city": "The Bronx",
        	"state": "FL",
        	"zipCode": "12345",
        	"countryCode": "us"
    	},
    	"storeId": null,
	    "signupCultureCode": "fr-CA"
    "registryUrl": "https://www.myregistrystaging.com/wedding-registry/roman-test-the-bronx-ny/1619821",
    "merchantRegistryUrl": "https://canadiantire.myregistrystaging.com/wedding-registry/roman-test-the-bronx-ny/1619821",

      "userWebsites": [
        {
          "websiteId": 199103,
          "relationType": 1
        }
      ]
    	},
	"eventId": "EVT:5b2bc287-a6a7-4e32-8abf-4408e46a81fb",
	"eventTime": "2024-10-23T21:01:18.4974543Z",
	"topic": "Registry.Signup",
	"dataVersion": "1.0"
}

Testing Webhook

  • Use tools like Webhook.site or RequestBin to inspect real payloads
  • Confirm endpoint is returning a 2xx status code
  • Non-2xx responses trigger retries until successful


Did this page help you?