Close connector for Python
Install with pip install dex-connector-close==0.1.0. The package requires
dex-connectors-sdk==0.1.0 and dex-python-sdk>=1.28.0, and implements the
manifest Queries listLeads and getLead with the same branches, defaults,
and failure classification as the Go module.
Operations
| Operation | Factory | Happy branch | Optional branches |
|---|---|---|---|
listLeads |
new_list_leads_step |
listed |
providerRejected, invalidResponse, defect |
getLead |
new_get_lead_step |
found |
notFound, providerRejected, invalidResponse, defect |
listLeads reads an offset page: skip is nonnegative and limit zero means
100, at most 100. getLead requires a Close lead ID that starts with lead_
and selects notFound for HTTP 404. 408, 409, 429, 5xx, and transport failures
retry; 401, 403, and other non-200 responses select providerRejected.
Authorization
Create a Dex Web connection named close as described in the
connector README. The API key travels only as the
HTTP Basic username and is resolved for every attempt.
Example
examples/close_lookup lists a page of leads
and reads the first one. Run the Worker with
uv run python -m examples.close_lookup.worker after dexcli dev has loaded a
project containing the close connection.
Tests
closemock.Mock scripts both Queries and defaults to the manifest answers.
Run uv run pytest tests for provider parity and manifest contract checks.
1 maintainer
Metadata
1 maintainer
Release files for dex-connector-close 0.1.0
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 |
|---|---|---|---|---|
| dex_connector_close-0.1.0.tar.gz | 70.9 kB | Without provenance | Details for dex_connector_close-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dex_connector_close-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for dex_connector_close-0.1.0-py3-none-any.whl |
Total release size: 86.9 kB
Release files / dex_connector_close-0.1.0.tar.gz
| Download URL | dex_connector_close-0.1.0.tar.gz |
|---|---|
| Size | 70.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
022ab9fa01c2fcdd585aa7b8ad1ab64c385128f1e00e0d4fdc17ddecb0e32fda
|
|
BLAKE2b-256 checksum How to use checksums |
61092e974781e1053180de481af26e34f9e680c60d3f0f73b7d32e55cdc3bc64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / dex_connector_close-0.1.0-py3-none-any.whl
| Download URL | dex_connector_close-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a41cb65c152557f59482a9583124896798b4caccde6b2bc527437d2cdcf41598
|
|
BLAKE2b-256 checksum How to use checksums |
2e776bf9760ad7a03e967583323e7eb3af18a2a8e9d6e65d4c2a36aa60f48798
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for dex-connector-close 0.1.0
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.
