============================
INTRODUCTION
-------------------------
This release provides access to the corresponding functionality through
both public API_KEY and private API_KEY.
The public API_KEY can access the file detection function of the cloud
sandbox. You need to register for a ThreatBook online account and view
your API Key through the Personal Center, which will be used for all your
API operations without submitting via the web, uploading the file/URL for
analysis and extracting the completed analysis. Report data. The
ThreatBook Online Sandbox API is a free service available for free websites
and programs. Please do not use the API for any commercial product or
service, as an alternative to an anti-virus product, or for any project that
may directly or indirectly damage the anti-virus industry.
The private API_KEY provides an easy way to invoke data from the
Threat Analytics Platform database and its detection and analysis
capabilities from any client. It includes the following functions:
file digital signature identification, new registered domain query,
email registration information query, domain analysis, IOC detection,
IP analysis, IP reputation query, etc. As our business customer or partner,
we will deliver your corresponding apikey by mail.
Directory structure
├── LICENSE
├── MANIFEST.in
├── my_api
│ ├── domain_analysis.py
│ ├── domain_query.py
│ ├── email_query.py
│ ├── fetch_file_legal_ca.py
│ ├── file.py
│ ├── __init__.py
│ ├── ioc.py
│ ├── ip_analysis.py
│ └── ip_reputation.py
├── README.rst
└── setup.py
Example
This is an example:
# import domain analysis
from my_api import domain_analysis
# create Create an instance object
test = domain_analysis.DomainAnalysis('your private api_key')
# Get the current whois information of the domain
info = test.get_cur_whois('domain to be queried ')
print(info)
Metadata
Release files for my-api 0.1.3
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 | Actions |
|---|---|---|---|---|
| my_api-0.1.3.tar.gz | 7.4 kB | Without provenance | Details for my_api-0.1.3.tar.gz |
Release files / my_api-0.1.3.tar.gz
| Download URL | my_api-0.1.3.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a98916729b10d7d6170759eb18d5b579728437ae4bba6cea55afc9d98da67ca4
|
|
BLAKE2b-256 checksum How to use checksums |
2b6892ddd31aa03ad4e920ee551f37bf96d1bb6d6ad7f8ae37fd0caa00da44bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.9.1 setuptools/20.7.0 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.5.2
|
Security for my-api 0.1.3
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.