Sign in
Status

Get subscription preferences for a specific contact

Retrieve a contact's current email subscription preferences.

get/communication-preferences/2026-03/statuses/{subscriberIdString}

Path parameters

subscriberIdStringstring required

The unique identifier of the subscriber whose communication preferences status is being retrieved.

Query parameters

channel'EMAIL' required

The communication channel for which the subscription status is being retrieved. This parameter is required and currently supports only 'EMAIL'.

businessUnitIdinteger

The ID of the business unit to filter the subscription status by. This is an optional parameter.

Response

successful operation

completedAtstring date-time required

The date and time when the operation was completed.

linksobject

Contains URLs related to the response, such as documentation or resources.

numErrorsinteger

The number of errors that occurred during the operation.

requestedAtstring date-time

The date and time when the request was made.

startedAtstring date-time required

The date and time when the operation started.

status'CANCELED' | 'COMPLETE' | 'PENDING' | 'PROCESSING' required

Indicates the current status of the operation, with possible values: PENDING, PROCESSING, CANCELED, COMPLETE.

Changes

Changed in 6 of the 14 revisions of this API.11

  • b0d8bc008db92See the full diff
    • ○

      the security scope communication_preferences.read was added to the endpoint's security scheme private_apps

      api-security-scope-added

    • ○

      the security scope communication_preferences.read_write was removed from the endpoint's security scheme private_apps

      api-security-scope-removed

    This revision also has 77 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 3578967e48df2See the full diff
    • ○

      the security scope communication_preferences.read was added to the endpoint's security scheme private_apps

      api-security-scope-added

    • ○

      the security scope communication_preferences.read_write was removed from the endpoint's security scheme private_apps

      api-security-scope-removed

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • e0403341222c2See the full diff
    • ○

      the security scope communication_preferences.read was added to the endpoint's security scheme private_apps

      api-security-scope-added

    • ○

      the security scope communication_preferences.read_write was removed from the endpoint's security scheme private_apps

      api-security-scope-removed

    This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • f33be5a826102See the full diff
    • ○

      the security scope communication_preferences.read was added to the endpoint's security scheme private_apps

      api-security-scope-added

    • ○

      the security scope communication_preferences.read_write was removed from the endpoint's security scheme private_apps

      api-security-scope-removed

  • dc2fdad57f7f2See the full diff
    • ○

      the security scope communication_preferences.read was added to the endpoint's security scheme private_apps

      api-security-scope-added

    • ○

      the security scope communication_preferences.read_write was removed from the endpoint's security scheme private_apps

      api-security-scope-removed

    This revision also has 129 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 62586336cea21See the full diff
    • ○

      endpoint added

      endpoint-added

    This revision also has 73 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Of the 14 revisions, 1 has no diff computed and 2 have a changelog that could not be searched.