karrio.veho
This package is a Veho extension of the karrio multi carrier shipping SDK.
Requirements
Python 3.11+
Installation
pip install karrio.veho
Usage
import karrio.sdk as karrio
from karrio.mappers.veho.settings import Settings
# Initialize a carrier gateway
veho = karrio.gateway["veho"].create(
Settings(
...
)
)
Check the Karrio Mutli-carrier SDK docs for Shipping API requests
1 maintainer
Metadata
1 maintainer
Release files for karrio-veho 2026.1.32
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| karrio_veho-2026.1.32-py3-none-any.whl | Python 3 | none | any | Details for karrio_veho-2026.1.32-py3-none-any.whl |
Release files / karrio_veho-2026.1.32-py3-none-any.whl
| Download URL | karrio_veho-2026.1.32-py3-none-any.whl |
|---|---|
| Size | 16.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
88b677f09452a2ac33a41363e901263631f3b09fb6a51c86ddfcce3dd96a0477
|
|
BLAKE2b-256 checksum How to use checksums |
dbe0a7dbecff4b36c5afed8af44ab5059d50f582dd8a9be94850ea4670bf6b2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for karrio-veho 2026.1.32
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.
