API Reference

The Zeckta Messaging API provides endpoints for SMS messaging, OTP verification, Sender Name management, and workspace operations. All requests require API key authentication.

All production API requests must be made over HTTPS.

Base URL

https://api.zeckta.com

Authentication

Include your API key in the Authorization header.

Authorization: Bearer YOUR_API_KEY

Response Format

All API responses follow a consistent structure:

{
  "success": true,
  "message": "Request completed successfully",
  "data": {},
  "requestId": "c1f6f0d9-7b7b-4f67-9d7f-fcfc7bdb0c63"
}

Available Resources

Resource	Description
SMS Messaging	Send SMS messages, campaigns, and track delivery status
OTP Service	Generate and verify one-time passwords
Sender Names	Register and manage sender identities
Workspace	Retrieve account and workspace information

Rate Limiting

API keys are subject to request rate limits. Rate limit information is returned in response headers:

X-RateLimit-Limit
X-RateLimit-Remaining
X-RateLimit-Reset

See the Authentication section for complete rate limiting details.

Error Handling

Standard HTTP status codes are used throughout the API.

Code	Meaning
200	Success
202	Accepted for processing
400	Invalid request
401	Authentication failed
404	Resource not found
409	Conflict
429	Rate limit exceeded
500	Internal server error

Overview

Endpoints

Introduction

API Reference

Base URL

Authentication

Response Format

Available Resources

Rate Limiting

Error Handling

Next Steps

Quickstart

Authentication

​API Reference

​Base URL

​Authentication

​Response Format

​Available Resources

​Rate Limiting

​Error Handling

​Next Steps

Quickstart

Authentication

API Reference

Base URL

Authentication

Response Format

Available Resources

Rate Limiting

Error Handling

Next Steps