toyota-na
Python client for Toyota North America service API
Install
pip install toyota-na
Usage
python -m toyota_na.app -h # Get help
python -m toyota_na.app authorize <username> <passworde>
python -m toyota_na.app get_user_vehicle_list # List vehicle
python -m toyota_na.app get_vehicle_status <vin> # Get vehcicle status
...
Known Issues
- Door/window status not always up-to-date unless you call
send_refresh_statusfirst and wait for it to complete (there is no notification that it completed successfully).
Developer Guide
Quick Start
from toyota_na.client import ToyotaOneClient
async def main():
cli = ToyotaOneClient()
await cli.auth.login(USERNAME, PASSWORD)
vehicle_list = await cli.get_user_vehicle_list()
vehicle_status = await cli.get_vehicle_status(vehicle_list[0]["vin"])
...
Abstracted Interface Example
from toyota_na.client import ToyotaOneClient
from toyota_na.vehicle.vehicle import get_vehicles
async def main():
cli = ToyotaOneClient()
Contributing
We use black and isort for opinionated formatting to ensure a consistent look and feel throughout the codebase no matter the contributor. Pre-commit is used to guarantee the files being checked-in to the repo are formatted correctly.
For convenience a vscode project settings file is included as well. Editors other than vscode will require some setup if you wish to have formatting take place while working.
Getting started:
- Install poetry - https://python-poetry.org/docs/#osx--linux--bashonwindows-install-instructions
- Clone the repo
poetry installpoetry shellpre-commit install
Samples
Sample responses from API calls are stored in samples folder. The data is sourced from real users and from the Toyota app's "Demo Mode"
Credits:
Thanks @DurgNomis-drol for making the original Toyota module and bring up the discussing of Toyota North America.
Thanks @visualage for finding the way to authenticate headlessly.
Metadata
Release files for toyota-na 2.1.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 | Actions |
|---|---|---|---|---|
| toyota-na-2.1.1.tar.gz | 13.3 kB | Without provenance | Details for toyota-na-2.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| toyota_na-2.1.1-py3-none-any.whl | Python 3 | none | any | Details for toyota_na-2.1.1-py3-none-any.whl |
Total release size: 31.1 kB
Release files / toyota-na-2.1.1.tar.gz
| Download URL | toyota-na-2.1.1.tar.gz |
|---|---|
| Size | 13.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a9c5b922ae9f9ea0a4f4ddff7f76ad181120965648a7346a4c427517c8caa772
|
|
BLAKE2b-256 checksum How to use checksums |
0c5745e0db16e4f8d2f1fe864205ee90adcc8a9b8451eec045f69f9a4b42acf3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.12
|
Release files / toyota_na-2.1.1-py3-none-any.whl
| Download URL | toyota_na-2.1.1-py3-none-any.whl |
|---|---|
| Size | 17.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
673dad3502b4b718620daa7dad0ab98ed73478eb242def352c6088e8249c6099
|
|
BLAKE2b-256 checksum How to use checksums |
24f127cf3348e1f1ad3a0687c5093e12e0d531ad7b864cd613d4811d2915d85e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.12
|
Security for toyota-na 2.1.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.
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.