Brandwatch API SDK
Introduction
The Brandwatch API SDK was designed to address many of the challenges involved in building complex applications which interact with RESTful API's in general and Brandwatch's API from Python 3, in particular:
- The SDK's object hierarchy roughly mirrors the API's resource hierarchy, making the code intuitive for those familiar with the Brandwatch platform
- All required parameters are enforced, and most optional parameters are supported and documented
- Typical Brandwatch workflows are supported behind the scenes; for instance, one can validate, upload, and backfill a query with a single function call
- The SDK is designed to support simple and readable code: sensible defaults are chosen for rarely used parameters and all resource IDs are handled behind the scenes
From the user's perspective, the basic structure of the SDK is as follows. One first creates an instance of the class BWProject; this class handles authentication (via a user name and password or API key) and keeps track of project-level data such as the project's ID. (Behind the scenes, the user-level operations are handled by the class BWUser from which BWProject is inherited.) One passes BWProject instance as an argument in the constructor for a series of classes which manage the various Brandwatch resources: queries, groups, tags, categories, etc. These resource classes manage all resource-level operations: for example a single BWQueries instance handles all HTTP requests associated with queries in its attached project.
Installation
Be sure to install the latest version of Python 3.x. You can install bwapi on your machine by running the following command:
pip install bwapi
This allows you to run scripts that import bwproject or bwresources from anywhere on your computer.
Examples
Please see the Jupyter notebook DEMO.ipynb for examples. This notebook was built as a beginner's guide to using the Brandwatch API SDK, so it has example code, as well as detailed instructions for use.
Disclaimer
This is not an official or supported Brandwatch library, and should be implemented at the users' own risk.
Metadata
Release files for bwapi 4.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 | Actions |
|---|---|---|---|---|
| bwapi-4.1.0.tar.gz | 29.5 kB | Without provenance | Details for bwapi-4.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bwapi-4.1.0-py35-none-any.whl | Python 3.5 | none | any | Details for bwapi-4.1.0-py35-none-any.whl |
Total release size: 57.4 kB
Release files / bwapi-4.1.0.tar.gz
| Download URL | bwapi-4.1.0.tar.gz |
|---|---|
| Size | 29.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cec7807414d179f73e49f938fbd628547c717e80135b3f94a991e1f61a947d2e
|
|
BLAKE2b-256 checksum How to use checksums |
1336b2e198018280990f937ea29dda7ec7dc3565f02e554c7280eb3405f338d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.2
|
Release files / bwapi-4.1.0-py35-none-any.whl
| Download URL | bwapi-4.1.0-py35-none-any.whl |
|---|---|
| Size | 27.9 kB |
| Tags | Python 3.5 |
|
SHA-256 checksum How to use checksums |
7f399c51f03df400f5ab426e1ead4c574e5851e0d530edd263ef24c209d7ce18
|
|
BLAKE2b-256 checksum How to use checksums |
2ac16f87c05a0ec0b58029a8a6f13b61f028a53e0d4fcad7aa1c515f7bfd0d4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.2
|
Security for bwapi 4.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.