getContactByEmail should expose idProperty
See original GitHub issueI would expect the contacts api to be able to get by email.
hubspot.crm.contacts.basicApi.getById(email);
But, from what I can see idProperty is not settable in the getById
const eventResponse = await hubspot.apiRequest({
method: "GET",
path: `/crm/v3/objects/contacts/${email}`,
qs: { idProperty: "email", properties: [] },
});
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:10 (1 by maintainers)
Top Results From Across the Web
getContactByEmail should expose idProperty #183 - bytemeta
getContactByEmail should expose idProperty #183. I would expect the contacts api to be able to get by email. hubspot.crm.contacts.basicApi.getById(email);.
Read more >API Integration - Get contact by email address
To use an email address as the unique identifier, set the idProperty as email and enter the email address in place of the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Yes, there are many ways to get the result. Although searching for a user and GETing a user by an identifier are very different. Also, the responses may be different. I wasn’t looking for a workaround, because yes, there are many; one I posted in the original post. The main motivation for some of the tickets is to align the API and the SDK. Options that are supported in the API should be exposed via the SDK in their corresponding methods.
An example would be
You can see from my original post this is supported by the API, just not the SDK.
I ended up writing my own library because of the inconsistencies I found.
@ksvirkou-hubspot see @dreadjr post above ^