qwicmail documentation

Everything you need to integrate qwicmail into your application, configure your sending domain, and understand the deliverability posture you're inheriting.

Start here

Pick the path that matches what you're trying to do.

Quickstart

From zero to a delivered receipt in about ten minutes — API key, domain verification, one curl call.

REST API reference

Authentication, idempotency, the /emails, /domains, and /webhooks resources, webhook payload schemas, and the full error code table.

SDKs

Official clients for TypeScript, Python, Go, Ruby, PHP, and Java/Kotlin. One-line install, idiomatic send, built-in webhook signature verification, automatic retry on 5xx.

Templates

Store re-usable HTML once, send with template_id + a data object. Liquid variables, partials, automatic plain-text fallback.

Webhooks

Receive delivery, bounce, complaint, and click events at your endpoint. HMAC-SHA256 signature verification with copy-paste recipes in every supported language.

Deliverability

DNS, DKIM, DMARC, IP reputation, and the warm-up curve every new tenant runs. What we manage for you and what you need to publish.

FAQ

Pricing, currencies, data residency, the closed-onboarding model, and how qwicmail differs from the providers you may have used before.

Conventions used in these docs

Base URL. All examples use https://api.qwicmail.com.
Authentication. Bearer token in the Authorization header. See Authentication.
JSON only. Requests and responses are application/json with snake_case fields.
Times. All timestamps are RFC 3339 in UTC.
IDs. All identifiers are UUIDs.
Code samples. The language picker above each example switches every block on the page; your choice persists across sessions.