HubSpot Integration

Hubspot Update Segment

Update a HubSpot segment's name and/or resolution config (refresh mode, interval, unresolved policy, method scope).

Required Scopes: lists:update (+ Full Suite plan)

patch/api/v1/integrations/hubspot/segments/{list_id}

Request

  • Base URL: https://api.sendseven.com
  • URL: https://api.sendseven.com/api/v1/integrations/hubspot/segments/{list_id}
  • Auth: HTTP bearer

Path parameters

list_idstring required

Request body

namestring nullable
refresh_mode'send_time' | 'cached'

How segment membership is resolved.

  • send_time (default) — resolve HubSpot membership live at send time; hubspot_segment_cache is never read/written.
  • cached — a scheduled refresh (every interval_minutes) resolves membership into hubspot_segment_cache; sends read from the cache.
interval_minutesinteger nullable
unresolved_policy'reachable_only' | 'skip' | 'all'

What to do with a HubSpot member that has no existing SendSeven contact.

  • reachable_only (default) — auto-create a contact ONLY when the member has a reachable identifier (valid phone and/or email); otherwise skip.
  • skip — never create; only send to already-existing contacts.
  • all — attempt to auto-create for every member (still subject to the platform's no-identifier ghost-contact guard).
method_scope'all_reachable' | 'single_preferred'

How many of a resolved contact's channels are targeted.

  • all_reachable (default) — one recipient per reachable, non-opted-out channel the contact has (email + phone + messenger id …). Matches how a native SendSeven dynamic list fans out.
  • single_preferred — collapse to a single preferred channel per contact.

Response

Successful Response

idstring required
tenant_idstring required
namestring required
descriptionstring nullable
list_typestring required
hubspot_connection_idstring nullable
hubspot_list_idstring nullable
hubspot_segment_configobject nullable
contact_countstring nullable
created_atstring date-time nullable
updated_atstring date-time nullable

Changes

No recorded changes to this operation across all 3 revisions of this API.