Hi everyone,
We are trying to post emails to our signup list in HubSpot. The issue is that some emails seem to be disregarded:
We are posting via the HubSpot Node package - any ideas why this could be?
Best,
Chris
Welcome, @Chris1904.
To clarify, are you using this endpoint to add contact records to a list?
If so, would you confirm your Hub ID and share an example payload, such as:
{
"vids": [ ],
"emails": [
"chris@email.co",
"chris+1@email.co",
"chris+1@email.com"
]
}
What did the endpoint return? Something like:
{
"updated": [
12345678,
13141516
],
"discarded": [
],
"invalidVids": [
],
"invalidEmails": [
chris+1@email.co
]
}
Please provide specific examples so I can troubleshoot effectively. If you do not want to share the full email addresses here, please share links to the contacts in question in your account (e.g. HubSpot).
message: ‘409 - {“message”:“Contact already exists”,“identityProfile”:{“vid”:53868328,“identity”:[{“value”:“hidden”,“type”:“EMAIL”,“timestamp”:1553625204309,“isPrimary”:true},",“requestId”:“ce1d3715a65dcb3ceb5534477c473066”}’
- Hope the vid and requestId will be enough for you to track down this event. So basically the endpoint is saying that a contact(email) like this already exists when I can confirm that this statement is false and an email like that doesn’t exist on the subscription list. Thanks in advance!
Hey, @Chris1904.
Thanks for that information. Unfortunately, individual calls are very difficult for me to locate on our back end, even with a requestId value.
Could you share the listId which you’re using for this endpoint? I’d like to try and replicate the issue.
Note for posterity:
Chris and I resolved this via direct message. The contacts were already members of the list in question, but he could not see them in the UI because he did not own the records and his permissions only allowed him to view owned and unassigned records.