Skip to main content
GET
JavaScript

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

section_id
string
required

Id of the workspace preference.

topic_id
string
required

Id of the subscription preference topic.

Response

A subscription preference topic in your workspace.

id
string
required

The preference topic id.

name
string
required

Human-readable name.

default_status
enum<string>
required

The default subscription status applied when a recipient has not set their own.

Available options:
OPTED_OUT,
OPTED_IN,
REQUIRED
routing_options
enum<string>[]
required

Default channels delivered for this topic. May be empty.

Available options:
direct_message,
email,
push,
sms,
webhook,
inbox
allowed_preferences
enum<string>[]
required

Preference controls a recipient may customize. May be empty.

A preference control a recipient may customize for a topic.

Available options:
snooze,
channel_preferences
include_unsubscribe_header
boolean
required

Whether a list-unsubscribe header is included on emails for this topic.

topic_data
object
required

Arbitrary metadata associated with the topic.

created
string
required

ISO-8601 timestamp of when the topic was created.

updated
string
required

ISO-8601 timestamp of the last update.

description
string | null

Optional description shown under the topic on the hosted preferences page.

digest
TopicDigestResponse · object | null

The topic's digest configuration, when one is set, and the only place a schedule's schedule_id is returned — the value the /digests/schedules/{schedule_id} endpoints are keyed by. Every read of a topic carries it, including the section and topic listings, so a digest can be located without a request per topic.

Absent rather than null on a topic with no digest, so "never configured" and "cleared" read the same way.

On a listing, absent can also mean the digest could not be read: those endpoints return the topics without their digests rather than failing outright, since listing preferences must not depend on the digest store being healthy. Read the single topic when the answer has to distinguish the two.

creator
string | null

Id of the creator.

updater
string | null

Id of the last updater.