Litemail Docs

Introduction

Welcome to Litemail — a modern email infrastructure built to help developers integrate, manage, and scale their email workflows. Whether you’re managing domains, creating workspaces, or handling subscriptions, the Litemail API gives you the flexibility to automate and extend your email services with ease.

This documentation will guide you through everything you need to start building on Litemail.

Authentication

Using Clerk JWT Tokens

All API requests require authentication with a Clerk-issued JWT token. Include it in the Authorization header as follows:

Authorization: Bearer <your-jwt-token>

If the token is missing or invalid, the API will return a 401 Unauthorized error.

Workspace Scoping

Some endpoints are scoped to specific workspaces. To target a workspace, include the following header:

x-workspace-key: <workspace-id>

If omitted, requests will default to the primary workspace associated with the authenticated user.

Base URL

All API requests should be made to:

https://api.litemail.app/v1

Rate Limits

To maintain performance and reliability, the Litemail API enforces rate limits:

5 requests per second per user (soft limit)

Burst allowance may temporarily allow short spikes.

If you exceed the rate limit, you’ll receive a 429 Too Many Requests response. Implement retries with exponential backoff to avoid interruptions.

Common Response Structure

Every successful response follows a consistent structure:

{
  "status": 200,
  "message": "Action completed successfully",
  "data": { ... }
}

Error responses include an HTTP status code and details about what went wrong:

{
  "status": 401,
  "message": "Unauthorized - Invalid or missing token"
}

Next Steps

Explore the Workspaces API to create and manage workspaces.

Use the Domains API to configure custom email domains.

Check out the Subscriptions API to manage plans and upgrades.

Litemail is designed to integrate seamlessly into your workflows — start building today!

Litemail Docs

Introduction#

Authentication#

Using Clerk JWT Tokens#

Workspace Scoping#

Base URL#

Rate Limits#

Common Response Structure#

Next Steps#