V1 Contacts Api endpoint equivalents not in CRM Api V3
Due to the deprecation of Hubspot Api Keys, I'm switching my app to a private app. My website updates my hubspot apps contact list on registration, however this no longer works now that I'm using the private app token as a header instead of passing the apiKey as a parameter. Looking at the documentation here https://developers.hubspot.com/docs/api/crm/contacts there doesn't seem to be equivalent parity with the old api here https://legacydocs.hubspot.com/docs/methods/contacts/create_or_update and the old api doesn't seem to support private app token. Will there be support for private app token in the legacy api? Or will I have to switch to the new api? Will the new api support the old apis endpoints?
V1 Contacts Api endpoint equivalents not in CRM Api V3
Hey @KMartinez82👋 I want to clarify my understanding. Are you asking if we can use the bearer token from a Private App when using this endpoint? Create or update a contact:
POST /contacts/v1/contact/createOrUpdate/email/:contact_email
If so, I ran a quick test using Postman and received an HTTP 200 response when using the token from a Private App. Here's what I did:
Created a Private App in my App Test Account
Set up the Authorization in Postman to Type = Bearer Token
V1 Contacts Api endpoint equivalents not in CRM Api V3
Hi Jaycee, This answers my question. I was under the impression that the createOrUpdate endpoint wouldn't work with the privateAppToken. Originally I had received a property values were not valid error and thought that perhaps the auth token didn't work. It seems that my properties are set as: