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

# System Overview

> Learn how Zeckta delivers SMS, campaigns, sender names, and OTP verification at scale.

Zeckta is a programmable messaging platform that enables developers and businesses to send SMS messages, manage Sender Names, run bulk campaigns, and verify users using one-time passwords (OTP).

Before using the API, create a Zeckta account and generate an API key from your dashboard.

<CardGroup cols={2}>
  <Card title="Base URL" icon="link">
    `https://api.zeckta.com/v1`
  </Card>

  <Card title="Authentication" icon="key">
    API key authentication is required for all requests.
  </Card>
</CardGroup>

***

## Core Services

<CardGroup cols={2}>
  <Card title="SMS Messaging" icon="message">
    Send transactional and application-to-person (A2P) SMS messages globally.
  </Card>

  <Card title="Campaigns" icon="megaphone">
    Deliver bulk messages to large recipient lists with delivery tracking.
  </Card>

  <Card title="Sender Names" icon="font">
    Register and manage branded Sender IDs for trusted messaging.
  </Card>

  <Card title="OTP Verification" icon="shield-check">
    Generate and verify one-time passwords for authentication workflows.
  </Card>
</CardGroup>

***

## Key Capabilities

* **High Throughput** — Designed for large-scale transactional messaging.
* **Asynchronous Processing** — Messages are queued and processed reliably.
* **Delivery Tracking** — Monitor message status from submission to delivery.
* **Workspace Isolation** — Resources are securely separated between workspaces.
* **Developer Friendly** — REST APIs, predictable responses, and OpenAPI documentation.

***

## Message Lifecycle

Every message follows a delivery lifecycle.

```text theme={null}
Queued
  ↓
Sending
  ↓
Sent
  ↓
Delivered
```

Messages may also transition to terminal states such as:

```text theme={null}
Failed
Rejected
Expired
```

See the Delivery Statuses guide for a complete status reference.

***

## Security Model

Zeckta uses workspace-based isolation.

Each API key belongs to a specific workspace and can only access resources created within that workspace, including:

* Messages
* Campaigns
* Sender Names
* OTP Sessions

Cross-workspace access is not permitted.

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Quickstart" href="/introduction/quickstart">
    Send your first message in minutes.
  </Card>

  <Card title="Authentication" href="/authentication/authentication">
    Learn how API key authentication works.
  </Card>
</CardGroup>