Volvo Cars API
This python library lets you use the Volvo Cars API. Authorisation follows the OAuth 2.0 authorisation code flow with PKCE.
Requirements
You'll need a Volvo Developers account and create an API application. Make sure to fill in all required fields and write down the retrieved client id and secret.
Usage
A script is worth a thousand words.
# Retrieved at the end of the API application registration process
client_id = "abc"
client_secret = "very-secret-key"
# Scopes that have been requested during the API application registration. You can also
# use less scopes than requested.
scopes = [
"openid",
"conve:battery_charge_level",
"conve:brake_status",
"conve:climatization_start_stop",
"conve:command_accessibility",
"conve:commands",
"conve:diagnostics_engine_status",
# ...
]
# Must be excactly as entered during the API application registration
redirect_uri = "htttps://my-volvo-application.io/callback"
# The VCC API key retrieved after the API application registration process
api_key = "abcdef-1234567890-abcdef"
client_session = _get_client_session()
# Authenticate
auth = VolvoCarsAuth(
client_session,
client_id=client_id,
client_secret=client_secret,
scopes=scopes,
redirect_uri=redirect_uri)
auth_uri = await auth.get_auth_uri() # optionally pass state
# Redirect user to auth_uri and wait for the callback
# ...
# Extract code from the callback url
code = _get_code_from_url()
await auth.async_request_token(code)
# The VIN must be linked to the account you sign in with
vin = "YV123456789012345"
# Create API client
api = VolvoCarsApi(client_session, auth, api_key, vin)
# Make API request
engine_warnings = await api.async_get_engine_warnings()
🚗 Powered by dreams
If you'd like to show your appreciation for this project, feel free to toss a coin to your dev. Donations help keep things running — and who knows, maybe one day they'll add up to a Volvo EX90 (hey, let me dream!). If you're feeling generous, you may donate one too — I'll even come pick it up! 😁
Release files for volvocarsapi 0.4.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| volvocarsapi-0.4.4.tar.gz | 31.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| volvocarsapi-0.4.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.8 kB
Release files / volvocarsapi-0.4.4.tar.gz
| Download URL | volvocarsapi-0.4.4.tar.gz |
|---|---|
| Size | 31.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bcd6341cf68d2f82fe669e2106d81129c329a222ce9b84663414cc7130cc08de
|
|
BLAKE2b-256 checksum How to use checksums |
c6c8134386daba41c5f2abe46bee96dab189834797bfb51cc96c08c171f3c941
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 21, 2026.
Transparency logRelease files / volvocarsapi-0.4.4-py3-none-any.whl
| Download URL | volvocarsapi-0.4.4-py3-none-any.whl |
|---|---|
| Size | 23.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1eb97ee3728d4d811dc592e4625d588768622c68c8629706239a12c141044b9
|
|
BLAKE2b-256 checksum How to use checksums |
b4cc82391e726cb6290a159c3011abe5c9e7cb9d6716db313943d3acc748921f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 21, 2026.
Transparency log