Docs

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

Send your first email

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

API reference

REST endpoints

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

Deliverability

DNS, DKIM, DMARC, and reputation

What records to publish, how we sign your mail, what we monitor, and how we handle bounces and complaints on your behalf.

FAQ

Common questions

Pricing, currencies, data residency, the closed-onboarding model, and the difference between qwicmail and the providers you may have used before.

SDKs

Official SDKs (TypeScript, Python, Go, Ruby) are on the Phase 5 roadmap. Until they ship, every endpoint can be driven from any HTTP client — the API is a small surface and the examples in this guide are all curl-based.

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.