Integrating the OTPDesk API
If you are building an automated registration bot, the OTPDesk API is designed for maximum speed. Our RESTful JSON endpoints allow you to purchase numbers, check balances, and poll for SMS codes with sub-50ms latency.
However, to maintain server stability for all developers, you must adhere to strict API integration rules.
Rate Limits and Polling Rules
The most common mistake developers make is polling the server too aggressively for an incoming SMS. Here is the exact logic you should implement to avoid an IP ban:
- Do NOT poll every second: It takes time for an SMS to travel from the app's server to our physical SIM farms.
- The 5-Second Rule: Set your script to wait exactly 5 seconds between each
GET /api/v1/order/statusrequest. Polling faster than this will trigger our DDoS firewall and block your server IP automatically. - Handle Errors Gracefully: If the API returns a 429 Too Many Requests error, your script must pause execution and implement exponential backoff.
Optimizing Your Success Rate
If your automated bot cancels too many numbers without receiving an SMS, your API key will be suspended. To prevent this, ensure your script validates the target website's status before requesting a number from OTPDesk. If the target app is down or blocking your proxies, halt your script immediately.
By following these rules, you can scale your operations to thousands of successful verifications per day without interruption. For endpoint specifications, visit your account dashboard to generate your unique API key.