This release is a pre-release and may not be stable for production use.
Data Access Platform Client Library
Data Access Platform (DAP) acts as a single source of data for analytics at Instructure. It provides efficient access to data collected across various educational products in bulk with high fidelity and low latency, adhering to a canonical data model.
We use analytics tools within the DAP CLI (Data Access Platform Command Line Interface) to help us understand how the tool is used, identify areas for improvement, and enhance the overall developer experience. No personal data is collected, stored, or shared through this analytics process. You can opt out of analytics tracking at any time by using the DAP CLI (Data Access Platform Command Line Interface). Please refer to the documentation for instructions on how to disable analytics through the CLI. For more information, please see our Privacy Policy.
Links to documentation
Metadata
Release files for instructure-dap-client 3.0.0rc1
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 | |
|---|---|---|---|---|
| instructure_dap_client-3.0.0rc1.tar.gz | 185.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| instructure_dap_client-3.0.0rc1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 429.0 kB
Release files / instructure_dap_client-3.0.0rc1.tar.gz
| Download URL | instructure_dap_client-3.0.0rc1.tar.gz |
|---|---|
| Size | 185.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ebe7bd92820e2cdf4b1885cf69ab9ecdd0b163bfeb4b07aad9ae86615a58f8e8
|
|
BLAKE2b-256 checksum How to use checksums |
1e6812775a4f12ca5861fd88b32153d99a8bd27e46ab47e6ff78cb7f29f838ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Oct 22, 2026.
Transparency logRelease files / instructure_dap_client-3.0.0rc1-py3-none-any.whl
| Download URL | instructure_dap_client-3.0.0rc1-py3-none-any.whl |
|---|---|
| Size | 243.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4cdfb11ff2be19bd88abe2d768aadddc4e1f139ca717ad2e87d630959eb83926
|
|
BLAKE2b-256 checksum How to use checksums |
b2fd43c067cb5106c262f93e3f47b30d0de4c43d404cdcc601532b63977dc615
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Oct 22, 2026.
Transparency logSecurity for instructure-dap-client 3.0.0rc1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for instructure_dap_client-3.0.0rc1.tar.gz
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 Oct 22, 2026.
Transparency logA 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.