> ## Documentation Index
> Fetch the complete documentation index at: https://dugble.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Developer-first email and SMS infrastructure for African startups and teams

Dugble provides APIs for transactional email and SMS, with additional messaging workflows for audiences, broadcasts, domains, sender identities, and delivery tracking.

<CardGroup cols={2}>
  <Card title="Email" icon="envelope" href="/docs/emails/introduction">
    Send transactional email, schedule delivery, attach files, and inspect message events.
  </Card>

  <Card title="SMS" icon="message-sms" href="/docs/sms/introduction">
    Send SMS, manage sender IDs, schedule messages, and track carrier outcomes.
  </Card>

  <Card title="Sender domains" icon="globe" href="/docs/domains/introduction">
    Authenticate the domains used for outbound email with DKIM and SPF.
  </Card>

  <Card title="API Reference" icon="square-terminal" href="/docs/api-reference/introduction">
    Explore request fields, responses, errors, and endpoint-level behavior.
  </Card>
</CardGroup>

## Start with a server-to-server integration

Dugble authenticates public API requests with team tokens. Keep tokens on your server and grant only the permissions your integration needs.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/docs/quickstart">
    Send your first transactional email and retrieve its delivery state.
  </Card>

  <Card title="Authentication" icon="key" href="/docs/authentication">
    Learn how team tokens, permissions, rotation, and revocation work.
  </Card>
</CardGroup>

## Asynchronous delivery

Email and SMS send requests are accepted asynchronously. A successful `202 Accepted` response means Dugble queued the message for delivery; it does not mean the recipient has received it yet.

Use message retrieval, delivery events, and supported webhook workflows to observe what happens after acceptance.