ABConnect
ABConnect is a Python package that provides a collection of tools for connecting and processing data for Annex Brands. It includes modules for quoting, building, and loading data from various file formats (CSV, JSON, XLSX), with a focus on handling unsupported characters and encoding issues seamlessly.
Table of Contents
Features
New in v0.1.8
- Generic Endpoint System: Automatic access to all 223+ API endpoints without manual implementation
- Fluent Query Builder: Build complex API queries with method chaining
- Pydantic Models: Type-safe response models with automatic validation
Core Features
- API Request Builder: Assemble dynamic API requests using static JSON templates and runtime updates.
- Quoter Module: Retrieve and parse quotes from the ABC API in both Quick Quote (qq) and Quote Request (qr) modes.
- Robust Data Loading: Supports CSV, JSON, and XLSX files with built-in encoding and character handling.
- Full API Client: Comprehensive API client with authentication and endpoint-specific methods.
Installation
You can install ABConnect using pip:
pip install ABConnect
For more detailed installation instructions and documentation, visit https://abconnecttools.readthedocs.io/
Configuration
Environment Variables
ABConnect requires the following environment variables for authentication:
# Create a .env file with your credentials
ABCONNECT_USERNAME=your_username
ABCONNECT_PASSWORD=your_password
ABC_CLIENT_ID=your_client_id
ABC_CLIENT_SECRET=your_client_secret
# Optional: Set environment (defaults to production)
ABC_ENVIRONMENT=staging # or 'production'
Using Different Environments
ABConnect supports both staging and production environments:
from ABConnect.api import ABConnectAPI
# Use staging environment
api = ABConnectAPI(env='staging')
# Use production environment (default)
api = ABConnectAPI()
# Environment can also be set via ABC_ENVIRONMENT variable
Testing Configuration
For testing, create a .env.staging file with staging credentials:
cp ABConnect/dotenv.sample .env.staging
# Edit .env.staging with your staging credentials
Tests will automatically use .env.staging when running with pytest.
Documentation
Full documentation is available at https://abconnecttools.readthedocs.io/
Development
To contribute to ABConnect, clone the repository and install in development mode:
git clone https://github.com/AnnexBrands/ABConnectTools.git
cd ABConnectTools
pip install -e .[dev]
Testing
Run all tests with:
pytest
Testing Model Implementation Against Swagger
ABConnect maintains strict alignment with the API's swagger specification. Several tests verify that all models and endpoints are properly implemented:
1. Test All Endpoints Have Implementations
# Comprehensive test with visual tree output showing which endpoints are implemented
pytest tests/api/swagger/test_all_swagger_endpoints_have_implementations.py -v
# Displays:
# ✅ Working endpoints with path count
# ❌ Missing endpoint files
# ⚠️ Import failures for endpoints that exist but can't be imported
2. Test Constitution Compliance
# Tests endpoint-model pairing and swagger-first principles
pytest tests/test_constitution.py -v
# Verifies:
# - All swagger endpoints have implementations
# - Endpoints have corresponding Pydantic models
# - No duplicate or violating files exist
3. Verify Model Imports
# Test that all models can be imported without errors
python -c "from ABConnect.api.models import shared, companies, contacts, job, address, jobtimeline; print('All model imports successful')"
# Test specific model validation and inspect fields
python -c "from ABConnect.api.models.jobparcelitems import ParcelItem; print(list(ParcelItem.model_fields.keys()))"
4. Run Specific Test Categories
# Test only API endpoints
pytest tests/api/ -v
# Test only models
pytest tests/api/models/ -v
# Test swagger compliance with detailed output
pytest tests/api/swagger/ -v -s
Test Coverage Summary
- Endpoint Tests: Verify all 223+ API endpoints are accessible
- Model Tests: Validate Pydantic models match swagger schemas
- Integration Tests: Test end-to-end API workflows
- Constitution Tests: Ensure code follows architecture principles
License
This project is licensed under the MIT License - see the LICENSE file for details.
Links
- Documentation: https://abconnecttools.readthedocs.io/
- Repository: https://github.com/AnnexBrands/ABConnectTools
- Issue Tracker: https://github.com/AnnexBrands/ABConnectTools/issues
- PyPI: https://pypi.org/project/ABConnect/
Metadata
Release files for ABConnect 0.2.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 | |
|---|---|---|---|---|
| abconnect-0.2.1.tar.gz | 223.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| abconnect-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 516.1 kB
Release files / abconnect-0.2.1.tar.gz
| Download URL | abconnect-0.2.1.tar.gz |
|---|---|
| Size | 223.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
30db77183e46574a5374fa7466ab4d544d149bd2c44dc22fdfe8b3a9678f3560
|
|
BLAKE2b-256 checksum How to use checksums |
92ed85c48baa772c80461aaedd14d0c1ec8242dfebe3825f8a94f361cd226604
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 5, 2026.
Transparency logRelease files / abconnect-0.2.1-py3-none-any.whl
| Download URL | abconnect-0.2.1-py3-none-any.whl |
|---|---|
| Size | 292.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11191abdbdad0b1793b30c6b398cd68c302ae380db2111ed753079e48a399a4a
|
|
BLAKE2b-256 checksum How to use checksums |
83a67edddbe552fc66ade060c6c5c097d72ed408510034291b5fc7ea4bec8d16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 5, 2026.
Transparency logSecurity for ABConnect 0.2.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 abconnect-0.2.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 Jan 5, 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.