I run LegitSMS, and we’re working on new features for the platform. Rather than guessing what users want, I’d rather ask directly. If you could change anything about current SMS verification providers, what would it be?
Examples:
Every suggestion is welcome. I’d rather build features people actually use than add things nobody needs.
The API should expose a verification as a lifecycle, not a purchase followed by ambiguous polling. For example: reserved → sms_sent → code_received → expired | cancelled → refunded, with each transition timestamped and queryable by a stable verification ID. The initial reservation request also needs an idempotency key, so a client timeout does not create an accidental second order.
Keep an immutable event history and optional webhooks using the same event IDs as the polling API. Failure responses should be machine-readable: provider_unavailable, number_not_assigned, message_timeout, refund_pending, rather than a generic failed status. Then the caller can distinguish “wait,” “retry safely,” and “start a new verification” without inferring state from timeouts.