safesmm
A small, dependency-free Python client for the SafeSMM API v2, the reseller API of SafeSMM (safesmm.net), an SMM panel for resellers and agencies.
It also works with any SMM panel that uses the standard API v2 format. Just pass a different api_url.
Install
pip install safesmm
Quick start
from safesmm import SafeSMM, SafeSMMError
client = SafeSMM("YOUR_API_KEY")
print(client.balance()) # {'balance': '12.50', 'currency': 'USD'}
for s in client.services()[:5]: # browse services
print(s["service"], s["name"], s["rate"], s["min"], s["max"])
order = client.add_order(service=1, link="https://t.me/yourchannel", quantity=1000)
print(order) # {'order': 23501}
print(client.status(order["order"]))
# {'charge': '0.27', 'start_count': '3572', 'status': 'In progress', 'remains': '157', 'currency': 'USD'}
All methods
| Method | API action | Notes |
|---|---|---|
balance() |
balance |
Your balance and currency |
services() |
services |
Full service list |
add_order(service, link, quantity, **extra) |
add |
Extra fields such as runs, interval (drip-feed) |
status(order_id) |
status |
One order |
multi_status([id1, id2]) |
status |
Several orders in one call |
refill(order_id) |
refill |
Services with a refill period |
cancel([id1, id2]) |
cancel |
Where cancel is available |
Errors returned by the API (for example Invalid API key.) are raised as SafeSMMError:
try:
client.balance()
except SafeSMMError as e:
print("API error:", e)
Using another panel
client = SafeSMM("KEY", api_url="https://example-panel.com/api/v2")
Security tips
- Keep your API key in an environment variable, not in your code or Git history.
- For bots and scripts, consider a separate panel account with only the balance you need.
Links
- SafeSMM website: https://safesmm.net
- API documentation: https://safesmm.net/api/docs
- More examples (PHP and Python): https://github.com/safesmmnet/safesmm-api-examples
License
MIT
Metadata
Release files for safesmm 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| safesmm-0.1.0.tar.gz | 4.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| safesmm-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.8 kB
Release files / safesmm-0.1.0.tar.gz
| Download URL | safesmm-0.1.0.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
add14567ec2385b7dda8295566415a81bc5650109477be94f82afdd275fd1384
|
|
BLAKE2b-256 checksum How to use checksums |
dfb4b048b149e0dae6a3ef2464cf31045008a7046b7b5e0c54640f14ace069ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / safesmm-0.1.0-py3-none-any.whl
| Download URL | safesmm-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f13598ff2beb80812889d7f1076bdebdb3ebbaf13e9c0ad0a0b0157987c1e6d9
|
|
BLAKE2b-256 checksum How to use checksums |
82517e671bc78cadedd68d46e967feafba3764b77c34b60c8bfed075f82f63a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for safesmm 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.