Skip to main content
A configuration set applies optional delivery settings to messages that select it. It does not change the verified identity required for sending.

Create and apply a configuration set

Open Email and Configuration sets, then click Create configuration set. Open the set to change sending, tracking, IP pool, and suppression overrides.
sending_enabled defaults to true. Disabling it rejects new sends through that set. Configuration is applied when a message is accepted, so editing a set does not rewrite messages already queued.

Open and click tracking

Tracking applies to HTML messages. Text-only messages are unchanged. Open tracking adds a pixel; click tracking rewrites eligible links to record a visit before redirecting. Recipient mail clients load these URLs automatically; they are not management APIs for SDK or CLI use. Opens and clicks measure recorded requests. Image blocking, mail proxies, security scanners, and repeated visits affect these counts. Do not interpret an open as proof that a person read the message. Aggregate events appear in Telemetry metrics; per-message engagement retains diagnostic counts and timestamps within its event-retention window.

Pool assignment and nullable updates

ip_pool in a response is a ResourceRef with id, crn, and optional name. On PATCH, omit ip_pool to preserve it, send a UUID/name/CRN to change it, or send {"ip_pool":null} to detach it. Empty strings are rejected. A pool contains account-owned dedicated IPs. If no eligible IP can be selected, sending falls back to shared platform IPs. The message’s outbound_ip records a dedicated address selected for that message.

Suppression overrides

suppression_overrides replaces the entire list when supplied; [] removes all overrides. You can also add or remove a single address through the nested /suppression-overrides endpoints. An override bypasses the account suppression for that address only on messages using this configuration set. Automatic suppressions come from bounce and complaint feedback. A manual suppression uses POST /v1/suppressions with address and optional description and expiration. The optional source_message response field identifies the message that caused a suppression. It is not a request selector.