Introduction

FutureSMS is built as production messaging infrastructure for serious cross-border traffic: high-throughput asynchronous dispatch, governed merchant and API-user access, template and sender controls, delivery-status normalization, callback processing, bulk execution, multi-currency pricing, multilingual operations, and finance-safe order handling. The platform is designed around durable business truth, secure account boundaries, double-entry ledger discipline, multiple accounting modes, traceable provider events, and operator visibility from request intake through reconciliation.

FutureSMS developer documentation is written for teams integrating merchant messaging, operational tracking, and supported third-party messaging products with FutureSMS.

Use this section to understand where each kind of information lives before you start implementing. The docs are split by reader task, not by backend module.

What is covered

The current documentation covers merchant-facing SMS integration: API login, shared request and response conventions, single-message sending, order tracking, bulk messaging, delivery report callbacks, Yeastar P-Series setup, and live API contract resources.

Use the workflow pages when you need implementation context and process logic. Use OpenAPI Docs, OpenAPI ReDoc, or the OpenAPI JSON when you need the exact live contract for fields, required flags, and schemas.

Account-specific setup

This documentation focuses on public integration behavior. For account credentials, sender and template enablement, billing setup, or environment-specific access, contact FutureSMS support or your account administrator.