Noimosiny Python SDK
Python client library for the Noimosiny API (OSINT and reverse-lookup platform).
Installation
Install the package via pip:
pip install noimosiny
Note: For local development, ensure dependencies are installed via pip install requests.
Quick Start
Initialize the Client using your API token (which can be obtained from the settings page on the Noimosiny dashboard). You can retrieve your balance and perform searches within a context manager block:
import os
from noimosiny import Client, NoimosinyError
def main():
# Load API token from environment
api_key = os.environ.get("NOIMOSINY_API_KEY", "your-api-key-here")
try:
# Use Client as a context manager for clean session closing
with Client(api_key) as client:
# Check account balances
gold = client.get_gold_credits()
silver = client.get_silver_credits()
print(f"Balances: Gold={gold} credits | Silver={silver} credits")
# Perform a reverse email lookup
print("Running reverse email lookup...")
results = client.search_email("user@example.com")
print("Results:", results)
except NoimosinyError as e:
print(f"API Error occurred: {e}")
if __name__ == "__main__":
main()
API Reference & Endpoints
Under the hood, the Noimosiny API routes all client actions to a single endpoint (POST https://api.noimosiny.com/v1/execute). The SDK abstracts this payload structure entirely into clean, pythonic method calls.
Rate Limits
- 5 simultaneous requests.
- 60 requests per minute.
Account & Balances
get_gold_credits() -> int
Retrieves your current Gold credit balance. Gold credits are consumed by reverse search queries (email, phone, username).
- Equivalent API payload method:
getGoldCredits - Example Return Value:
1000
get_silver_credits() -> int
Retrieves your current Silver credit balance. Silver credits are consumed by advanced tool queries.
- Equivalent API payload method:
getSilverCredits - Example Return Value:
5000
Reverse Search Operations
All search operations return a python dictionary matching the API's standard response format. Each query will scan several internal modules and return success statuses along with metadata from matches.
search_email(email: str) -> dict
Perform a reverse email lookup to find associated social media profiles and online registration records.
- Equivalent API payload parameter:
"type": "reverse_email" - Response Format Example:
{ "type": "reverse_email", "query": "user@example.com", "results": [ { "module": "TikTok", "success": true, "data": { "id": "70397021345678", "likes": 28506, "region": "Australia", "videos": 792, "private": false, "language": "en", "username": "johndoe", "verified": false, "followers": 1029, "following": 670, "created_at": "2021-12-10 00:14:02", "profile_url": "https://tiktok.com/@johndoe", "display_name": "John Doe", "social_profiles": { "youtube": "John Doe" } } } ] }
search_phone(phone: str) -> dict
Perform a reverse phone number search to find ownership details, carrier details, and geographical location info.
- Equivalent API payload parameter:
"type": "reverse_phone" - Response Format Example:
{ "type": "reverse_phone", "query": "+1234567890", "results": [ { "module": "PhoneUS1", "success": true, "data": { "zip": "12345", "city": "New York", "name": "John Doe", "type": "Landline", "state": "NY", "county": "New York", "carrier": "WINDSTREAM NUVOX, INC. - FL", "latitude": "40.7128", "longitude": "-74.0060", "risk_scale": 0.6, "risk_description": "possibly unsafe caller" } } ] }
search_username(username: str) -> dict
Perform a reverse search on a username to check registry status and profiles across multiple social networks.
- Equivalent API payload parameter:
"type": "reverse_username" - Response Format Example:
{ "type": "reverse_username", "query": "johndoe", "results": [ { "module": "Instagram", "success": true, "data": { "url": "https://instagram.com/johndoe", "username": "johndoe", "image": "https://scontent-atl3-1.cdninstagram.com/v/............", "followers_count": 918, "following_count": 0, "posts_count": 0, "is_private": true, "is_verified": false, "is_business": false, "is_professional": false } } ] }
Error Handling
All SDK-specific exceptions subclass NoimosinyError. Catching it handles any API or connection issue:
from noimosiny import Client
from noimosiny.exceptions import (
NoimosinyError,
AuthenticationError,
RateLimitError,
InsufficientCreditsError,
BadRequestError,
ServerError
)
try:
with Client("API_KEY") as client:
client.search_email("test@example.com")
except AuthenticationError:
print("Invalid API Key.")
except RateLimitError:
print("Too many requests. Please throttle your queries.")
except InsufficientCreditsError:
print("Your account is out of credits.")
except BadRequestError as e:
print(f"Invalid query parameters: {e}")
except ServerError:
print("An unexpected server-side error occurred on the Noimosiny API.")
except NoimosinyError as e:
print(f"Generic SDK error: {e}")
Exception Hierarchy
NoimosinyError(Base exception class)AuthenticationError(401 Unauthorized)RateLimitError(429 Too Many Requests)APIRequestError(Base for request validation & API responses)BadRequestError(400 Bad Request)InsufficientCreditsError(403 Forbidden)APITimeoutError(408 Request Timeout)ServerError(500+ Internal Server Error)
Metadata
Release files for noimosiny 1.0.1
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 | |
|---|---|---|---|---|
| noimosiny-1.0.1.tar.gz | 6.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| noimosiny-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.9 kB
Release files / noimosiny-1.0.1.tar.gz
| Download URL | noimosiny-1.0.1.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3ec8c5d66a21f78c90fa318b417e6b97aa38fa28fdb929894f98a74990203204
|
|
BLAKE2b-256 checksum How to use checksums |
6f7adf4fa6a34a96277449f52015a623fbac30e461c9d7980db46f1b01f973eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 4, 2026.
Transparency logRelease files / noimosiny-1.0.1-py3-none-any.whl
| Download URL | noimosiny-1.0.1-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e030eb49609b97c36abe5682207c96bedc8fccdec0b7cc3d588711546ab029a0
|
|
BLAKE2b-256 checksum How to use checksums |
af865173f45c2dd21dd43b094b21869eec3e64cad12dcbc75a9f2c26d61c88ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 4, 2026.
Transparency logSecurity for noimosiny 1.0.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for noimosiny-1.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 4, 2026.
Transparency logA 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.