topic Re: /crm/v3/objects/engagements Endpoint in APIs & Integrations

/crm/v3/objects/engagements Endpoint

AY512 — Fri, 07 Nov 2025 22:10:16 GMT

In the docs, there are endpoints for notes, tasks, meetings, emails, and calls such as
- /crm/v3/objects/notes/search
- /crm/v3/objects/tasks/search
etc

My understanding is that these are all categorized as 'engagements,' but there is no equivalent search endpoint for all engagements in the API docs. However, I've found that the route /crm/v3/objects/engagements/search DOES work. Is this an endpoint we're allowed to use?

Thanks

Re: /crm/v3/objects/engagements Endpoint

STierney — Fri, 07 Nov 2025 22:38:14 GMT

Hey @AY512 - thanks for posting in the Community!

I'd like to tag in some subject matter experts to see what insight they may have on this inquiry! @karstenkoehler, @danmoyle, @franksteiner79 - any thoughts for @AY512?

Shane, Senior Community Moderator

Re: /crm/v3/objects/engagements Endpoint

evaldas — Sat, 08 Nov 2025 19:49:06 GMT

Hi @AY512,

There is no documentation for this specific object search via the API, but it is a part of the supported object types that can be used with the CRM Search API. So, yes, you are allowed to use it 🙂

Just keep in mind that since it is not officially documented, support may not be available and, while unlikely, there is also a possibility that the functionality may no longer be available in the future.

Re: /crm/v3/objects/engagements Endpoint

RubenBurdin — Fri, 28 Nov 2025 19:08:14 GMT

Hi @AY512 , good catch spotting that route. HubSpot does treat notes, tasks, calls, emails, and meetings under the broader “engagement” umbrella, so it’s natural to expect a unified search endpoint even though the docs only list the individual object searches.

The CRM Search API is flexible enough that querying the parent object works, but since /crm/v3/objects/engagements/search isn’t officially documented, it sits in that grey area where it behaves like a first-class endpoint but doesn’t come with guarantees. If you plan to rely on it, I’d keep an eye on the object schema and the supported types list so you’ll spot any changes early

The safer long-term pattern is still querying each engagement type explicitly when you need predictable support. If you eventually need these engagement records reflected in another system without juggling multiple endpoints, Stacksync keeps HubSpot objects aligned in real time so you don’t have to stitch the data together manually.