Using Search APIs alone instead of GET call

[Iffbld01]

Hi,

Can someone please explain the difference between following two APIs:

1. /crm/v3/objects/contacts and 

2. /crm/v3/objects/contacts/search

I know the below points:

1 - GET call, pass limit and properties filters as query parameters. 

2 - POST call, pass limit and other filters in the request body. Can search using different operators (EQ, NEQ etc.).

I want to decide whether using #2 alone will give me all the data that I can get using #1? Or is there something additional that is returned by #1, which cannot be retreieved using #2?

Thanks.

[Jaycee_Lewis]

Hey, @Iffbld01 👋 Thanks for reaching out. From my perspective, you have covered the main points, e.g. request params vs including properties in the body.

One difference you might want to consider is how you want to return associations:

• Contacts API 
• Search API (using pseudo-property values)

It's really going to come down to your needs. The search API offers more options. My suggestion is to make a simple request to both endpoints for the same data and compare how each is returned. Not fancy, but it might help give clarity to your specific use-case and needs. 

Best,

Jaycee