Skip to main content

Digitea Licensing Python SDK

Official Python client for the Digitea Runtime Licensing API.

The public facade is DigiteaLicensing. The OpenAPI-generated transport under generated/ is an implementation detail.

Installation

python -m pip install digitea-licensing==1.2.3

Quick star

from digitea_licensing import DigiteaLicensing

client = DigiteaLicensing(
    product_id="prd_example123",
    timeout=10.0,
    retries=2,
)

activation = client.activate(
    license_key="dgt_lic_example",
    instance_id="stable-installation-id",
    instance_name="Customer workstation",
)

if activation.valid and activation.status == "ACTIVE":
    start_application()

The SDK persists an installation identity by default. Pass an explicit instance_id or provide an InstanceIdStore implementation when the application owns its secure storage.

Complete lifecycle

validation = client.validate(
    license_key,
    instance_id="stable-installation-id",
)

if validation.valid and validation.status == "ACTIVE":
    enable_licensed_features()

deactivation = client.deactivate(
    license_key,
    instance_id="stable-installation-id",
)

Renewal session and idempotency

renewal = client.create_renewal_session(
    license_key,
    instance_id="stable-installation-id",
    idempotency_key="renewal-operation-123",
    return_url="https://software.example.com/license-renewal",
)

open_in_browser(renewal.checkout_url)

# Run after the browser returns; the redirect is not proof of payment.
renewal_status = client.get_renewal_session_status(
    license_key,
    renewal.renewal_session_id,
    instance_id="stable-installation-id",
)
if renewal_status.status == "PAID":
    validation = client.validate(license_key, instance_id="stable-installation-id")

The Python SDK supports return_url on create_renewal_session and get_renewal_session_status for server-confirmed renewal flows.

Reuse the same idempotency_key when retrying the same logical renewal operation. If omitted, the SDK generates a valid key and reuses it across HTTP retries.

Configuration

client = DigiteaLicensing(
    product_id="prd_example123",
    base_url="https://api.getdigitea.com",
    timeout=10.0,
    retries=2,
)

Runtime calls use only product_id, license_key and instance_id. No Developer API key is accepted or required.

Errors

from digitea_licensing import DigiteaError

try:
    result = client.validate(license_key)
except DigiteaError as error:
    print(error.code, error.status)
    if error.code == "LICENSE_EXPIRED":
        show_renewal_screen()
    elif error.code in {"NETWORK_ERROR", "TEMPORARILY_UNAVAILABLE"}:
        show_temporary_connection_error()

Digitea error codes are preserved. Temporary network, rate-limit and server failures are retried; definitive licensing decisions are not.

Security

Never embed a Developer API key, webhook secret or server credential in distributed Python software. Never log a license key. Use HTTPS in production.

Published on PyPI; this SDK does not have a dedicated public GitHub repository. See the documentation for the supported integration guide.

The same four operations are available in every Runtime SDK:

  • activate()
  • validate()
  • deactivate()
  • create_renewal_session()
  • get_renewal_session_status()

Metadata

Release files for digitea-licensing 1.2.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for digitea-licensing 1.2.3
File Size Uploaded Provenance Actions
digitea_licensing-1.2.3.tar.gz 30.2 kB Without provenance Details for digitea_licensing-1.2.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for digitea-licensing 1.2.3
File Interpreter ABI Platform Actions
digitea_licensing-1.2.3-py3-none-any.whl Python 3 none any Details for digitea_licensing-1.2.3-py3-none-any.whl

Total release size: 79.8 kB

Release files / digitea_licensing-1.2.3.tar.gz

Download URL digitea_licensing-1.2.3.tar.gz
Size 30.2 kB
Tags Source
SHA-256 checksum
How to use checksums
10bf12538fb25373427a560a2542ea0738e400f5aff6619ea37805dd8827d001
BLAKE2b-256 checksum
How to use checksums
8d3a350b27e39debe7fd8381a2781ea3bda6bcd95b45d85b1910ee64672e31da
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.13

Release files / digitea_licensing-1.2.3-py3-none-any.whl

Download URL digitea_licensing-1.2.3-py3-none-any.whl
Size 49.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c2c3427505e7265a4b82c02385c7f4f87da500e19474c30c76f3c1a0479c3b5e
BLAKE2b-256 checksum
How to use checksums
ddab18048198247265af3e9abbaeda79ed91f1fee679e30032b0d65d4ed43b76
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.13

Security for digitea-licensing 1.2.3

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page