What you can build with the Noir SMS API (and what you cannot)

A Telegram or Discord bot that sells verifications

A bot is a natural interface for a single verification: the user picks a service and a country, pays the bot owner, gets a number in the chat and receives the code a few seconds later. Your backend calls GET /services to build the menu, POST /numbers with max_price to buy, and listens for the signed sms.received webhook to post the code back into the right chat. If the number expires, the price returns to your balance and your bot should refund the user too.

A bot that sells to the public is a reseller, so the reseller rules apply in full: your users must follow the Noir SMS Acceptable Use Policy, you are responsible for abuse through your bot, and accounts that resell to abusers are closed. Also follow Telegram's or Discord's own bot and payment rules.

An internal tool so employees don't use personal numbers

Marketing, support and operations teams constantly sign up for tools that want a phone number. When people use their personal phones, the company loses access when they leave, and their private number ends up in vendor databases. A small internal page backed by the API can hand out a number for one verification and show the code, with the cost charged to one company balance and every purchase listed by GET /numbers?status=all.

Be honest with your team about the limits: numbers are single use and recycled later. For accounts the company keeps, the tool should prompt staff to add a durable recovery method, such as a shared mailbox or an authenticator app, right after verifying.

# Nothing arrived and cancelable_at has passed: cancel and get the price back
curl -X POST https://noirsms.com/api/v1/numbers/6026e15f-088d-45b5-bf22-70ed0b417afa/cancel \
  -H "Authorization: Bearer nsk_live_YOUR_KEY"

# Code arrived and you need a second SMS on the same number (free while open)
curl -X POST https://noirsms.com/api/v1/numbers/6026e15f-088d-45b5-bf22-70ed0b417afa/resend \
  -H "Authorization: Bearer nsk_live_YOUR_KEY"

Testing how your OTP SMS looks in many countries

If your app sends verification codes worldwide, the SMS a user receives in Canada, the UK or Brazil can differ from what you see at home: a different sender format, a translated template, a stripped character, a message split in two. By receiving your own OTP on real numbers from many countries, you can read sms[].text exactly as it arrived and check language, length and branding. GET /countries tells you where numbers are in stock today.

import requests

BASE = "https://noirsms.com/api/v1"
H = {"Authorization": "Bearer nsk_live_YOUR_KEY"}

# Which countries have numbers in stock right now?
countries = requests.get(f"{BASE}/countries", headers=H).json()["countries"]
for c in countries[:10]:
    services = requests.get(f"{BASE}/services", params={"country": c["country"]}, headers=H).json()["services"]
    print(c["country"], len(services), "services in stock")

A privacy layer for your own accounts

Some developers build a personal tool that verifies their own accounts with a temporary number, so their real phone number is not tied to every newsletter, marketplace or test environment they sign up for. That is the same use as the dashboard, just scripted. The same caution applies: for any account you plan to keep, add your own phone, email or authenticator afterwards, because the rented number will not be available for recovery later.

Not allowed

These uses are prohibited by the Noir SMS Acceptable Use Policy whether you use the dashboard, the API or a reseller. Accounts involved in them are closed, and resellers whose customers do them lose their account too.

• Bulk or automated account creation on any platform, including farming accounts for sale.
• Evading bans, suspensions or limits, including re-registering after a ban with a new number.
• Spam, unsolicited bulk messaging, and fake engagement such as reviews, votes or followers.
• Fraud, scams, impersonation and harassment.
• Bypassing bank, fintech, payment, crypto-exchange or identity (KYC) verification.

Step by step

1. Check the fitMake sure your idea serves legitimate accounts owned by you or by customers who follow the Acceptable Use Policy.
2. Build on the APIUse /services and /countries for menus, POST /numbers to buy, and the sms.received webhook to deliver codes.
3. Handle the edgesRefund users when numbers expire, cancel unused numbers after 2 minutes, and remind users to add their own recovery method.