Fabman API
Library for interfacing with the Fabman API. Created for Texas Inventionworks as part of the Cockrell School of Engineering at the University of Texas at Austin.
Official documentation for the Fabman API can be found here. Live interaction and description of all endpoints can further be found here. This library is currently targeting version 2.3.1 of the Fabman API.
Getting Started
To get started, simply install using pip:
pip install fabman
which will install the latest stable release for your use. Note that this library is in active, heavy development and the API may change with little warning. To use the latest state of this repo, use the following command:
pip install git+https://github.com/utexas-engr-tiw/fabman-api
To start interacting with the Fabman API, simply provide your API key:
from fabman import Fabman
API_KEY = 'abcdef-123456789-a1b2c3d4e5f6a7b8'
f = Fabman(API_KEY)
...
From there, you can begin interacting with api endpoints as described in the official documentation. Most top-level methods return an object which manages that object. For example, to get a single member and update that member's name,
member = f.get_member(12345)
member.update(firstName="Kira", lastName="Nerys")
All parameters except for IDs are taken in as kwargs and should follow the camelCase naming conventions found on the Fabman API. Moreover, the library performs minimal checking of parameters, leaving that to the Fabman API. For required fields for create and update fields, refer to the Live Fabman API Documentation. The one exception to this is the lockVersion requirement for update methods. All update methods will automatically add the current lockVersion parameter to the body.
Refer to the library documentation more information on this library.
Contributing
We would love contributions! We are a small development team. To contribute, familiarize yourself with the code, the layout, make your edits and a pull request. We currently need help with
- Real life testing of the API
- Documentation
Metadata
Release files for fabman 1.2.10
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 | |
|---|---|---|---|---|
| fabman-1.2.10.tar.gz | 35.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fabman-1.2.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 67.9 kB
Release files / fabman-1.2.10.tar.gz
| Download URL | fabman-1.2.10.tar.gz |
|---|---|
| Size | 35.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
812025dffcc71249d37f2e7e614a35e301a6fefe6983e9aac8f94e7037d8608f
|
|
BLAKE2b-256 checksum How to use checksums |
43567b1ec6c964f834d76dc1ec43be4263c4985f0d0fca633c6ecc03228bb821
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Release files / fabman-1.2.10-py3-none-any.whl
| Download URL | fabman-1.2.10-py3-none-any.whl |
|---|---|
| Size | 32.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1fcceeec24ba8c13eb5ef7df40777950421429199727d9faaf5805bdfae99069
|
|
BLAKE2b-256 checksum How to use checksums |
0d80bff1656e28701aec8014b2c5163c75d4a9852811e42e5411df899506faa6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Security for fabman 1.2.10
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.