The DaisySMS 替代方案 面向开发者
DaisySMS shut down in March 2026 — here is where its users went.
DaisySMS 已于 26 March 2026 关闭，不再出售号码。“DaisySMS has shut down on March 26, 2026.”此页面保留给当初对接了它的人：下表对比它曾提供的内容与我们的服务，迁移部分展示你需要改动的两行。
DaisySMS was known for simple US verification numbers. It shut down on 26 March 2026; its own site now says so and sells nothing. Eveses offers the same instant-OTP experience across 190+ countries, with a full REST API, SDKs and webhooks for teams that automate.
团队为什么从 DaisySMS 转向 Eveses
Clean REST API with idempotency keys, webhooks, and official JS / Python / Go / PHP SDKs.
Automatic refunds when an OTP never arrives — you only pay for delivered codes.
One wallet, one key, no KYC — top up with crypto or card and start in minutes.
DaisySMS 在这些情况下仍可能更合适： Nothing, now: DaisySMS stopped serving customers in March 2026. If you liked it for US-only verification from a minimal dashboard, the closest thing here is a single US number bought from the explorer rather than the API.
Eveses 与 DaisySMS — 常见问题
▸What happened to DaisySMS?
▸Does Eveses cover the US like DaisySMS did?
▸Is there an API?
▸How fast do codes arrive?
用代码迁移到 Eveses
Your whole integration is two calls — buy a number, read the code. Plain HTTP (no SDK required), but official SDKs exist for JS, Python, Go and PHP.
# 1 · Buy a number
curl -X POST https://api.eveses.com/api/v1/numbers/orders \
-H "Authorization: Bearer $EVESES_API_KEY" \
-d '{"country":"ua","service":"telegram"}'
# → { "id": "…", "phone": "+380…", "status": "waiting" }
# 2 · Read the OTP (or subscribe to a webhook)
curl https://api.eveses.com/api/v1/numbers/orders/<id> \
-H "Authorization: Bearer $EVESES_API_KEY"
# → { "status": "sms_received", "sms": [{ "code": "123456" }] }Prefer push over polling? Subscribe to the activation.sms_received webhook and skip step 2 entirely.