On this page
  1. Install
  2. Construct a quiet Resend client
  3. Bind provider work to durable intent
  4. API entry points and requirements
  5. Peer dependencies

This guide describes upcoming source contracts, not a publication receipt. Check release availability and keep your complete Playstack graph on one verified version.

@playstack/audiences-resend

Resend Contacts and Segments as an explicit remote authority for Playstack audiences.

Reference: @playstack/audiences-resend@0.1.0-beta.5 · TypeScript

Pro. Covered by the Playstack Pro License. Registry access is required; check preview availability before installing. See package access.

@playstack/audiences-resend maps Playstack subscription commands and recipient pages to Resend Contacts and Segments. Consent, confirmation and suppression remain in @playstack/audiences.

Install

After confirming preview access, install the package at your application's shared Playstack version:

sh
npm install --save-exact @playstack/audiences-resend@0.1.0-beta.5

Check the peer requirements below before choosing a runtime or provider.

Construct a quiet Resend client

ts
import { Resend } from 'resend'
import {
  createResendAudiencesClient,
  resendAudienceAuthority,
} from '@playstack/audiences-resend'

const resend = createResendAudiencesClient(Resend, {
  apiKey: config.resendApiKey,
  timeoutMs: 30_000,
  maximumResponseBytes: 1_048_576,
})
const authority = resendAudienceAuthority({
  client: resend,
  resolveSegmentId: ({ list, segment }) => segmentIds[segment?.key ?? list.key],
})

The factory retains the actual SDK instance and its Contacts/Segments types. Its public transport override uses the fixed https://api.resend.com origin, owns authorization headers and avoids the SDK's raw error logging in every environment. It does not change global console behavior or NODE_ENV.

The default transport performs one fetch without internal retries and refuses redirects. Each request has independent cancellation and a 30-second default deadline. Successful JSON bodies have a default 1 MiB limit, configurable up to 4 MiB. Error bodies are discarded without parsing or logging; returned diagnostics use fixed messages and allowlisted status information rather than raw provider messages, response headers or causes.

Structural injected clients remain supported and retain responsibility for their own privacy, retries and transport behavior. A factory fetch override is a trusted seam: it must honor cancellation, avoid retries and refuse redirects. Passing an arbitrary SDK constructor or transport does not qualify its behavior. The package does not read environment variables or bundle the Resend SDK.

Bind provider work to durable intent

Use the authority with the native Audiences remote processor, its journal and registering queue. Queue admission and original intent registration share a physical transaction. The processor owns the committed dispatch claim, factual provider acknowledgement, native projection and uncertainty barriers. Direct authority.apply calls are unmanaged and do not provide those durable guarantees.

Local prepare snapshots the operation, email and resolved segment ID without making a provider request. Its commitment binds the processor's journal to that selection, and its submission closure can be used once. Changed segment configuration cannot silently retarget an admitted retry. Configure a new processor provider instance identity when changing the physical provider account.

Only failure before the first mutation can produce an exact command/key-bound AudienceRemoteNotSubmittedError. After entering any create, update, segment-add or segment-remove method, errors remain uncertain. A successful contact update followed by a failed segment addition is therefore quarantined by the processor, rather than automatically replayed. Malformed success receipts are also uncertain; HTTP status alone never proves the complete operation was not submitted.

Removing a subscription removes only its segment membership; it does not delete the contact or globally unsubscribe it. A new explicit subscription clears global unsubscribe state because it represents fresh consent. Keep native consent and suppression checks in the Audiences composition.

API entry points and requirements

Reference snapshot: @playstack/audiences-resend@0.1.0-beta.5. Import only the entry point your runtime needs. Paths below are relative to the installed package; use Go to Definition in your editor to inspect exact parameters, return types and overloads. Do not import the declaration-file paths directly.

Public entry pointDeclaration file
@playstack/audiences-resend./dist/index.d.ts
@playstack/audiences-resend/package.jsonNo TypeScript declaration (asset or metadata export).

Node.js engine requirement: >=20. This is not a claim that every entry point works in browsers or Workers.

Peer dependencies

Keep existing framework versions that satisfy these ranges. Install optional peers only when using the corresponding adapter. The package manager resolves ordinary dependencies separately.

PeerCompatible rangeWhen needed
@playstack/audiences0.1.0-beta.5Required by the package.

For a complete first program, start with Getting started. For API lookup and partial-example conventions, see Reading the reference. Provider failures, lifecycle requirements and application responsibilities remain described in the guide above; types alone do not establish production safety.

Go

Playstack Pro tag
OriginsPricingBlogChangelogStatus

© 2026 Playstack. All rights reserved.

With OSS

By

Commune Software