Skip to the documentation
TypeScript

nextmail.segments

Every method in this namespace: its signature, its parameters, what it returns and an example.

Methods

Saved conditions on contacts, such as opened in the last 90 days or a custom field, that narrow a broadcast to the people who match: save, change and delete them, and count who they match.

nextmail.segments.list()

List the saved segments

Scopesaudiences:read
Signature
list(options?: RequestScope): Promise<Array<SegmentResource>>

Resolves every saved segment of the workspace as a plain array, newest first, each with its name, its description and its conditions. A workspace keeps at most 100, so the list is never paged.

A segment holds no contacts of its own. Who matches is worked out each time it is read, so use preview to count the matches and pass a segment id as segmentId to broadcasts.send to narrow a broadcast with it.

Parameters

options.signalAbortSignal

Cancels the request.

options.apiKeystring

Overrides the client's API key for this call only.

Returns

Array<SegmentResource>, each with id, name, description, definition, createdAt and updatedAt.

Example

const segments = await nextmail.segments.list() for (const segment of segments) console.log(segment.id, segment.name, segment.definition.conditions.length)

Notes

  • The SDK retries it after a network failure or a retryable status, since it changes nothing.

  • Segments belong to the workspace, not to the key or the person who made them.

Also available in

API
GET /segments
Python
segments.list()
Ruby
segments.list
PHP
segments->list
Go
Segments.List
Java
segments().list
C#
Segments.ListAsync
CLI
nextmail segments list

nextmail.segments.get()

Get one segment

Scopesaudiences:read
Signature
get(id: string, options?: RequestScope): Promise<SegmentResource>

Fetches one saved segment by its id, with match and every condition in definition. The conditions come back as they were saved, so the object can be edited and passed to update or preview as it is.

Parameters

idstringRequired

Segment id such as seg_5d2a9c7e1b4f08a36c1e9b42.

options.signalAbortSignal

Cancels the request.

options.apiKeystring

Overrides the client's API key for this call only.

Returns

SegmentResource.

Example

const segment = await nextmail.segments.get('seg_5d2a9c7e1b4f08a36c1e9b42') console.log(segment.name, segment.definition.match, segment.definition.conditions)

Notes

  • A segment from another workspace, or one that was deleted, is a 404 segment_not_found.

Also available in

API
GET /segments/{id}
Python
segments.get()
Ruby
segments.get
PHP
segments->get
Go
Segments.Get
Java
segments().get
C#
Segments.GetAsync
CLI
nextmail segments get

nextmail.segments.create()

Save a segment

Scopesaudiences:write
Signature
create(body: SegmentCreate, options?: RequestScope): Promise<SegmentResource>

Saves a set of conditions under a name. definition.match is all (the default) when a contact has to meet every condition, or any when one is enough, and definition.conditions holds 1 to 20 of them.

Each condition names a field and an operator. email takes is, is_not, contains, not_contains and ends_with, and name takes those but ends_with, plus is_set and is_not_set. source takes is and is_not with how the contact was added. created, opened, clicked and engaged take within_days and not_within_days with days: when the contact was added, the last time they opened or clicked a tracked email from the workspace, and the later of those two. audience takes in and not_in with audienceId, and counts only subscribed members. event takes within_days and not_within_days with event, a name sent with events.send, and days. attribute takes key, the name of a custom field on the contact, with the operators name takes. Text is compared without regard to case.

Nothing is sent and no contact changes. A segment is used by passing its id as segmentId to broadcasts.send.

Parameters

body.namestringRequired

What the segment is called, 1 to 120 characters.

body.descriptionstring | null

A longer note, up to 500 characters.

body.definitionSegmentDefinitionInputRequired

{ match?: 'all' | 'any', conditions: Array<SegmentCondition> } with 1 to 20 conditions.

options.signalAbortSignal

Cancels the request.

options.apiKeystring

Overrides the client's API key for this call only.

Returns

SegmentResource with the new seg_ id.

Example

const segment = await nextmail.segments.create({    name: 'Opened in the last 90 days',    definition: {        match: 'all',        conditions: [{ field: 'opened', operator: 'within_days', days: 90 }]    }}) await nextmail.broadcasts.send({    audienceIds: ['aud_4c1b8e2a7d9f05c36b4e8a71'],    segmentId: segment.id,    from: 'Acme <news@acme.com>',    subject: 'Thanks for reading',    text: 'Hi {{firstName|there}}, here is something for our regular readers.'})

Notes

  • A workspace keeps at most 100 segments. The 101st is refused with 409 segment_limit_reached.

  • An audience condition that names an audience the workspace does not have is a 404 audience_not_found, and an operator its field does not take is a 422 invalid_parameter.

  • The SDK does not retry a create after a network failure, so a retry after a lost response can save two. List them and delete the spare.

Also available in

API
POST /segments
Python
segments.create()
Ruby
segments.create
PHP
segments->create
Go
Segments.Create
Java
segments().create
C#
Segments.CreateAsync
CLI
nextmail segments create

nextmail.segments.update()

Change a segment

Scopesaudiences:write
Signature
update(id: string, patch: SegmentPatch, options?: RequestScope): Promise<SegmentResource>

A partial update: a field you leave out keeps what it holds. Sending definition replaces match and every condition at once, and description: null takes the description away.

A broadcast already sent or scheduled keeps the conditions it was given, so a change here only reaches the broadcasts sent after it.

Parameters

idstringRequired

The seg_ id of the segment.

patch.namestring

A new name, 1 to 120 characters.

patch.descriptionstring | null

A new note. Null takes it away.

patch.definitionSegmentDefinitionInput

New conditions, replacing the old ones.

options.signalAbortSignal

Cancels the request.

options.apiKeystring

Overrides the client's API key for this call only.

Returns

SegmentResource as it stands after the change.

Example

const segment = await nextmail.segments.update('seg_5d2a9c7e1b4f08a36c1e9b42', {    name: 'Opened in the last 30 days',    definition: { conditions: [{ field: 'opened', operator: 'within_days', days: 30 }] }}) console.log(segment.updatedAt)

Notes

  • The SDK retries it after a network failure, since sending the same change twice leaves the same segment.

  • A segment from another workspace is a 404 segment_not_found.

Also available in

API
PATCH /segments/{id}
Python
segments.update()
Ruby
segments.update
PHP
segments->update
Go
Segments.Update
Java
segments().update
C#
Segments.UpdateAsync
CLI
nextmail segments update

nextmail.segments.delete()

Delete a segment

Scopesaudiences:write
Signature
delete(id: string, options?: RequestScope): Promise<DeletedSegmentResource>

Deletes the saved segment. No contact is touched, and a broadcast already sent or scheduled keeps the conditions it was given.

A draft that still names the segment in segmentId is refused with 404 segment_not_found when it is sent, until it names another segment or none.

Parameters

idstringRequired

The seg_ id of the segment.

options.signalAbortSignal

Cancels the request.

options.apiKeystring

Overrides the client's API key for this call only.

Returns

DeletedSegmentResource, { object: 'segment', id, deleted: true }.

Example

const removed = await nextmail.segments.delete('seg_5d2a9c7e1b4f08a36c1e9b42') console.log(removed.id, removed.deleted)

Notes

  • The SDK does not retry a delete. A 404 on your own second attempt after a lost response means the first one worked.

Also available in

API
DELETE /segments/{id}
Python
segments.delete()
Ruby
segments.delete
PHP
segments->delete
Go
Segments.Delete
Java
segments().delete
C#
Segments.DeleteAsync
CLI
nextmail segments delete

nextmail.segments.preview()

Count the contacts a segment matches

Scopesaudiences:read
Signature
preview(body: SegmentPreviewInput, options?: RequestScope): Promise<SegmentPreviewResource>

Counts the contacts a set of conditions matches now and returns up to 10 of them, without saving or sending anything. Pass the definition of a saved segment to count it, or new conditions to try them first.

With audienceIds, only the subscribed members of those audiences count, which is the number a broadcast to them with this segment would start from before unsubscribes and suppressions are taken out. broadcasts.preview with segmentId gives that final number.

Parameters

body.definitionSegmentDefinitionInputRequired

The conditions to count, as create takes them.

body.audienceIdsArray<string>

Up to 10 audiences. Only their subscribed members count. Left out, every contact of the workspace counts.

options.signalAbortSignal

Cancels the request.

options.apiKeystring

Overrides the client's API key for this call only.

Returns

SegmentPreviewResource with contacts, the number that match, and sample, up to 10 of them.

Example

const preview = await nextmail.segments.preview({    definition: { conditions: [{ field: 'engaged', operator: 'not_within_days', days: 180 }] },    audienceIds: ['aud_4c1b8e2a7d9f05c36b4e8a71']}) console.log(`${preview.contacts} people have not opened or clicked in six months`)

Notes

  • A condition on a custom field reads each contact it checks and stops at 20,000 of them, answering 422 segment_too_large. Narrow it with audienceIds first.

  • The SDK retries it after a network failure or a retryable status, since it changes nothing.

Also available in

API
POST /segments/preview
Python
segments.preview()
Ruby
segments.preview
PHP
segments->preview
Go
Segments.Preview
Java
segments().preview
C#
Segments.PreviewAsync
CLI
nextmail segments preview