CarConnectivity Connector for Seat and Cupra Vehicles
CarConnectivity is a python API to connect to various car services. This connector enables the integration of seat and cupra vehicles through the MyCupra API. Look at CarConnectivity for other supported brands.
Configuration
In your carconnectivity.json configuration add a section for the seatcupra connector like this:
{
"carConnectivity": {
"connectors": [
{
"type": "seatcupra",
"config": {
"brand": "cupra",
"username": "test@test.de",
"password": "testpassword123"
}
}
]
}
}
brand (seat or cupra) defines what login is used. MyCupra or MySeat account. Your credentials will work with both, but you may need to consent again to the terms and conditions when you use the "wrong" brand.
Credentials
If you do not want to provide your username or password inside the configuration you have to create a ".netrc" file at the appropriate location (usually this is your home folder):
# For MyCupra
machine seatcupra
login test@test.de
password testpassword123
In this case the configuration needs to look like this:
{
"carConnectivity": {
"connectors": [
{
"type": "seatcupra",
"config": {
}
}
]
}
}
You can also provide the location of the netrc file in the configuration.
{
"carConnectivity": {
"connectors": [
{
"type": "seatcupra",
"config": {
"netrc": "/some/path/on/your/filesystem"
}
}
]
}
}
The optional S-PIN needed for some commands can be provided in the account section of the netrc:
# For MyCupra
machine seatcupra
login test@test.de
password testpassword123
account 1234
Known issues
Unexpected keys found
Not all items that are presented in the data from the server are already implemented by the connector. Feel free to report interesting findings in your log data in the Discussions section or as an Issue (Enhancement). My time is very limited, so usually new features take some time to get into the library, also because I need to align functionallity between the connectors of all brands.
1 maintainer
Metadata
1 maintainer
Release files for carconnectivity-connector-seatcupra 0.6.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 | |
|---|---|---|---|
| carconnectivity_connector_seatcupra-0.6.4.tar.gz | 48.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| carconnectivity_connector_seatcupra-0.6.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 99.6 kB
Release files / carconnectivity_connector_seatcupra-0.6.4.tar.gz
| Download URL | carconnectivity_connector_seatcupra-0.6.4.tar.gz |
|---|---|
| Size | 48.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0fde7dcc1af87032269d5b703b104f4a4a49714e9ca9ac09e4dfcb68356b8d49
|
|
BLAKE2b-256 checksum How to use checksums |
8f9222a058d13bef5be412419a1f69c6f0d287f07a5d26dd410a66c944f0958f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 5, 2026.
Transparency logRelease files / carconnectivity_connector_seatcupra-0.6.4-py3-none-any.whl
| Download URL | carconnectivity_connector_seatcupra-0.6.4-py3-none-any.whl |
|---|---|
| Size | 51.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f2d5f2b606de5f9cc1bfbb0e2b0b0268ac9277ce80bd45b6cdd71b327b368b4a
|
|
BLAKE2b-256 checksum How to use checksums |
0a49b655cfd966400815c720ad409d6e61911e2461814f8b3ecba5764a46077b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 5, 2026.
Transparency log
