Title here
Summary here
API overview
The Platfone provides a variety of APIs to cater to different use cases. Each API is designed to handle specific tasks, ensuring that you can choose the right tool for your needs.
This page helps you understand and compare the available APIs for SMS-based service activations using temporary mobile numbers.
🧭 Choosing the Right API
| API Name | Best For | Key Highlights |
|---|---|---|
| Activation API | App developers automating SMS activations | Simple, reliable, quality-first; pay only on SMS received |
| Retail API | Resellers managing their own customers and balances | Full account/balance control; fast app development |
| Alternative API | Legacy users migrating from other SMS activation platforms | Quick migration with minimal changes to existing code |
🔍 API Comparison
| Feature | Activation API | Retail API | Alternative API |
|---|---|---|---|
| Use Case | Integrate SMS activation into your app | Build a customer-facing app | Migrate from legacy SMS APIs |
| Balance Management | Project-level only | Per-customer & project-level | Project-level only |
| Order Numbers | ✅ | ✅ (per customer) | ✅ |
| Receive SMS/OTP | ✅ | ✅ (per customer) | ✅ |
| Retry Activation | ✅ | ✅ (per customer) | ✅ |
| Cancel Activation | ✅ | ✅ (per customer) | ✅ |
| Activation History | ✅ | ✅ (per customer) | ✅ |
| View Balance | ✅ | ✅ (per customer) | ✅ |
| Supported Countries / Services | ✅ | ✅ | ✅ (limited 1) |
| Price Cap (per activation) | ✅ | ✅ | ✅ |
| Order retry (with new price) | ✅ | ✅ | ❌ |
| Define quality preference during order | ✅ | ✅ | ❌ |
| API Simplicity | Modern RESTful | RESTful with customer context | GET/POST legacy format |
| Integration Time | Short | Medium | Short |
| Versioning & Compatibility | Backward-compatible | Backward-compatible | Compatible with legacy SMS APIs |
| Billing Policy | Only on SMS received | Only on SMS received | Only on SMS received |
| Sandbox Environment | ✅ | ✅ | ✅ |
🧪 API Overview Cards
🟢 Activation API
Who it’s for: Developers needing a simple API to order temporary numbers and receive SMS codes.
Why use it: Fast integration, quality-focused, no billing unless SMS is received.
Key strengths:
- Price/quality-based number selection
- Refunds via SMS report endpoint
- Detailed activation and billing responses
- Great for software, platforms or SaaS providers
🔵 Retail API
Who it’s for: Businesses who need to onboard end users, manage customer balances, and act as resellers.
Why use it: Full control over customers and balances with almost zero database footprint.
Key strengths:
- Multi-user balance management
- Transaction history per customer
- Ideal for consumer-facing applications
🟡 Alternative API
Who it’s for: Users migrating from other SMS services with legacy-style APIs.
Why use it: Familiar structure and parameters, smooth migration path.
Key strengths:
- Legacy GET/POST support
- Quick drop-in replacement
- Minimal refactor for existing codebases
🚀 How to Choose
Just want to activate and receive SMS codes easily?
🟢 Use Activation API
Building customer facing product with SMS activations?
🔵 Use Retail API
Already using another SMS provider and switching?
🟡 Use Alternative API
📘 Still Not Sure?
- Start with Activation API if you’re building an app or testing the waters.
- Use Retail API if you’re building solution for customers.
- Try Alternative API if your current codebase uses a legacy structure.
Choose your tool
Explore more tools available on Platfone
Alternative API supports a limited set of countries and services compared to the other APIs. ↩︎
Next
Activation API