HubSpot 404 error with incoming data

[aalthaus_revriv]

Hi there! In my zap between Zapier's Email Parser and HubSpot, I received a 404 error. The Zapier support team sent the following info related to that error message, but we cannot make heads or tails of it:

Credentials are censored and data may be formatted and/or truncated.

REQUEST

POST https://api.hubapi.com/contacts/v1/contact/createOrUpdate/email/Phone%201:%20(702)%20303-7600 Email...

Content-Length: 15123
Accept-Encoding: gzip, deflate
Accept: application/json
User-Agent: Zapier
Connection: keep-alive
Content-Type: application/json; charset=utf-8

{
"properties": [{
"property": "sa_lead_project_req_s_overview",
"value": "Key Features: They need to be able to run reports on different conversion metrics of how long interviews are taking, conversion rates, and things along those lines. They need to be able to send email and text message to candidates through the system and schedule interviews with them. They need the system to be able to track the overall process of turning a candidate into an employee. They need the system to be able to track where each candidate is coming from if possible. | Deployment: Annual Revenue: $26 million to $50 million\n\nNumber of Users: 6 to 10 users. 6.\n\n\n\nProject & Requirements Overview\n\nApplications needed: Applicant Tracking and On-Boarding\n\nKey features needed: They need to be able to run reports on different conversion metrics of how long interviews are taking, conversion rates, and things along those lines. They need to be able to send email and text message to candidates through the system and schedule interviews with them. They need the system to be able to track the overall process of turning a candidate into an employee. They need the system to be able to track where each candidate is coming from if possible.\n\nDeployment: Web-based | Currently Using: Key features needed: They need to be able to run reports on different conversion metrics of how long interviews are taking, conversion rates, and things along those lines. They need to be able to send email and text message to candidates through the system and schedule interviews with them. They need the system to be able to track the overall process of turning a candidate into an employee. They need the system to be able to track where each candidate is coming from if possible.\n\nDeployment: Web-based\n\nCurrently using: They are using email, Excel spreadsheets, and other manual methods to track this information. | Reasons for Shopping: Key features needed: They need to be able to run reports on different conversion metrics of how long interviews are taking, conversion rates, and things along those lines. They need to be able to send email and text message to candidates through the system and schedule interviews with them. They need the system to be able to track the overall process of turning a candidate into an employee. They need the system to be able to track where each candidate is coming from if possible.\n\nDeployment: Web-based\n\nCurrently using: They are using email, Excel spreadsheets, and other manual methods to track this information.\n\nReasons for shopping: They need to be able to streamline workflow, track applicant intake more carefully, and save as much time in the recruiting process as possible. | Evaluated: They need to be able to run reports on different conversion metrics of how long interviews are taking, conversion rates, and things along those lines. They need to be able to send email and text message to candidates through the system and schedule interviews with them. They need the system to be able to track the overall process of turning a candidate into an employee. They need the system to be able to track where each candidate is coming from if possible.\n\nDeployment: Web-based\n\nCurrently using: They are using email, Excel spreadsheets, and other manual methods to track this information.\n\nReasons for shopping: They need to be able to streamline workflow, track applicant intake more carefully, and save as much time in the recruiting process as possible.\n

---

RESPONSE

404

Date: Wed, 28 Mar 2018 22:34:05 GMT
Content-Length: 0
Connection: keep-alive
Set-Cookie: __cfduid=ddf0804d6e99db6d53ec4c8ad5de07c831522276445; expires=Thu, 28-Mar-19 22:34:05 GMT; path=/; domain=.hubapi.com; HttpOnly
Access-Control-Allow-Credentials: false
Vary: Accept-Encoding, Accept-Encoding
Expect-Ct: max-age=604800, report-uri="[redacted]"
Server: cloudflare
Cf-Ray: 402d8fe5bf819568-IAD

[Derek_Gervais]

Hi @adaume_revriv,

Does the request URL contain all of the information shown in your post, or is that a formatting quirk? The 'Create or update a contact' endpoint URL takes the following form:

contacts/v1/contact/createOrUpdate/email/:contact_email

Where :contact_email is replaced by the email address of the contact you're trying to create/update. If you're appending all of the information listed above, you're seeing a 404 because HubSpot can't parse that info as a valid email address. Most of that information should be sent in the POST body, while just the email address (in this example, rherman@superiortileandmarble.com) should be passed in the URL. The correct URL in this example should look like this:

POST contacts/v1/contact/createOrUpdate/email/rherman@superiortileandmarble.com

Zapier will need to alter the request(s) they're making to this endpoint according to the following docs in order for the requests to function correctly:

developers.hubspot.com

Create or update a contact

POST /contacts/v1/contact/createOrUpdate/email/:contact_email - Create a contact if it doesn't exist in a portal already, or update it with the latest property values if it does.