Frequently asked questions

PulsePigeon sends transactional, lifecycle, and marketing email through the REST API, customer campaigns, and event-driven automations. SMTP submission is a separately approved compatibility path during controlled rollout, not an automatically enabled transport.

Yes. Create an account at /register with Google sign-in, or use a work email and confirm the verification link. Both paths provision the free workspace immediately without a sales call. The Free plan includes 3,000 emails per month, 500 active contacts, one verified sending domain, and 7-day logs.

Yes. Create a free account, then use /billing to subscribe, upgrade, downgrade, cancel, or reactivate through Stripe Checkout and the Stripe Customer Portal. Refund requests are reviewed and executed by two authorized operators; there is no customer-side refund button.

Use POST /v1/messages for retry-safe API sending. The SMTP submission gateway appears at /smtp only for approved tenants after the production TLS, DNS, listener, and external-smoke gates pass. It requires STARTTLS and separate project-scoped credentials.

No. Signup and workspace provisioning complete in the same verified registration flow. Production sending still requires domain readiness, and accounts that trigger abuse signals can be held for manual risk review.

The send is rejected before acceptance with HTTP 402 or 429 when a hard limit would be exceeded. It is not sent or converted into an automatic overage.

Both are enforced independently: a monthly send cap and an active-contact cap for each plan tier.

Mail uses separate critical, transactional, briefing, marketing, and third-party routing and reputation controls. This limits spillover, but a shared provider or platform incident can still affect more than one lane.

Transactional or relationship treatment depends on message purpose, recipient relationship, and jurisdiction. Marketing consent, identification, and unsubscribe duties also vary by jurisdiction. PulsePigeon provides policy controls, but this FAQ is not legal advice. Review maintained guidance and consult counsel for your use case.

Adding a domain generates SPF, DKIM, and DMARC records and tracks each verification result. Google, Yahoo, and Microsoft impose additional authentication requirements for high-volume senders. Their policies change, so review current primary guidance before a large launch.

Authentication is necessary but not sufficient. Mailbox providers also weigh sender reputation, engagement, volume patterns, and content signals. Passing DNS checks never guarantees inbox placement.

The platform includes authenticated blocklist and DMARC aggregate-report ingestion with operator views for alignment, disposition, and authentication results. Those views explicitly report disabled, stale, or no-data feed states. Monitoring is active only after the production feed is configured and verified.

Sending uses reputation-managed shared pools by default, with quarantine controls for tenants showing abuse signals. Scale and Enterprise tenants can request a dedicated IP. This is not an instant self-serve toggle. Inventory, assignment, and warm-up are implemented and operator-gated. Forced owned-MTA routing and verified source-IP binding on the delivery MTA are also implemented. Activation requires a real address, DNS and provider authorization, production enablement, and an external recipient send that verifies the observed source IP.

No. Templates use named variables, HTML and plain-text bodies, validation, and linting through the API. The visual workflow builder is not an email-template builder.

Yes. POST /v1/messages accepts an optional Idempotency-Key. Repeating the same key and body returns the original result; reusing a key with a different body returns 409.

Python and TypeScript SDK betas are in staged release validation. Public support begins only after registry, clean-install, and sandbox-send verification. The cURL tab remains available as the public REST path.

Yes. The authenticated /campaigns composer lets customers select a segment and published template, inspect a suppression-safe audience estimate, schedule or send, and review delivery results. Campaigns enter the marketing lane.

Yes. Automations use versioned visual workflows with send, wait, condition, weighted split, and stop nodes. You can validate and publish an immutable version, pause or resume it, inspect run and step history, and replay eligible failed runs.

Yes. POST /v1/messages/batch accepts 1 to 100 independently personalized items with per-item idempotency and partial results.

Yes. Subscriber lists can require confirmation before an address becomes subscribed.

There is no public CLI package today. A source-only CLI exists in the private product repository; the REST API remains the public integration path while SDK betas complete release validation.

Configure signed HMAC-SHA256 status webhooks at /webhooks. Deliveries use exponential-backoff retries and dead-letter handling, and message events are also visible in the console.

Plan targets are 7 days on Free, 30 on Starter, 90 on Growth, and 365 on Scale. The scheduled purge audit runs automatically in dry-run mode by default. Real deletion remains evidence-gated until a fresh backup, scratch restore, and reviewed production dry run are recorded.

Hard-bounce and complaint suppression is automatic. Hosted RFC 8058 unsubscribe is injected for marketing mail when the public base URL is configured. Multi-recipient marketing sends fan out so each recipient gets its own token, To header, and delivery. Transactional, security, and billing categories do not receive an unsubscribe header.

No. PulsePigeon has its own API rather than emulating another provider's request shape. Public migration guides cover six providers; tenant-wide suppression import remains an authenticated console operation rather than a project-key SDK method.

Scale and Enterprise can submit and validate SES configuration after trust and billing checks, but dispatch through tenant credentials is not wired yet. Sends continue through PulsePigeon's platform infrastructure.

PulsePigeon does not provide a drag-and-drop template builder, public AI copywriting assistant, React Email-style compiler, SMS, push, or WhatsApp sending. MCP and agent routes exist for signed product sessions but are not public project-key integrations.

Use the support desk for product questions, deliverability incidents, and account access issues. AI-assisted answers appear only when a selected provider is configured and ready.