> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paubox.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Quickstart guide
> In this Quickstart, send your first HIPAA compliant email via Paubox Email API in under 5 minutes.
It's free to [sign up](https://www.paubox.com/pricing/paubox-email-api) and to send up to 300 emails per month with Paubox Email API. Visit our [sign up page](https://www.paubox.com/pricing/paubox-email-api) and create an account.
**Note:**
If you send more than 300 emails in one month, you will be automatically moved to the appropriate [pricing tier](https://www.paubox.com/pricing/paubox-email-api) and billed the annual cost.
Once you have a Paubox account, go to the [Paubox Email API > Settings](https://next.paubox.com/emailapi/settings) page and add the domain you'll be sending from.
Paubox will display a **TXT record** to add to your domain's DNS provider (e.g., Route 53, Cloudflare, GoDaddy). Copy the verification string and add it as a new TXT record at your DNS provider, then return to the Settings page and click **Verify**.
**Tip:**
Most DNS providers propagate TXT records within a few minutes, but allow up to 48 hours. If verification fails immediately, wait a few minutes and try again.
From the [Paubox Email API > Settings](https://next.paubox.com/emailapi/settings) page, click on the domain you would like to generate an API key for, then press the **Add API Key** button. Give the key a description and a new key will be generated upon submission.
You can generate several API keys to use in different applications as needed. Make sure you save your key because if you lose it you will have to generate a new one.
Note the **customer endpoint** shown on the same Settings page. It takes the form:
```
https://api.paubox.net/v1/YOUR_USERNAME
```
You will use this base URL in every API request.
Use the following curl command to send a test email. Replace `YOUR_USERNAME`, `YOUR_API_KEY`, and the `from` address with your actual values. The `from` address must match your verified domain.
```bash theme={null}
curl --request POST \
--url https://api.paubox.net/v1/YOUR_USERNAME/messages \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"data": {
"message": {
"recipients": ["recipient@example.com"],
"headers": {
"subject": "Hello from Paubox",
"from": "sender@yourdomain.com"
},
"content": {
"text/plain": "Hello world",
"text/html": "Hello world
"
}
}
}
}'
```
**What success looks like:**
A `200 OK` response confirms your message was accepted for delivery:
```json theme={null}
{
"sourceTrackingId": "3d38ab13-0af8-4028-bd45-52e882e0d584",
"data": "Service OK"
}
```
Save the `sourceTrackingId`; you can use it to check delivery status later.
Official SDKs handle authentication and request formatting for you. Choose your language:
* [C#](/csharp-sdk/quickstart)
* [Go](/go-sdk/quickstart)
* [Java](/java-sdk/quickstart)
* [Node.js](/node-sdk/quickstart)
* [Perl](/perl-sdk/quickstart)
* [PHP](/php-sdk/quickstart)
* [Python](/python-sdk/quickstart)
* [Rails](/rails-sdk/quickstart)
* [Ruby](/ruby-sdk/quickstart)
* [Rust](/rust-sdk/quickstart)
Prefer the terminal? See the [CLI quickstart](/cli/quickstart) to send email without writing code.
## Next steps
Check delivery status using a sourceTrackingId
Add files to your messages via the REST API
Use Paubox from AI agents and editors via MCP