Skip to main content

Paradime

Paradime - Python SDK

Installation

pip install paradime-io

SDK Usage

Generate your API credentials from Paradime workspace settings.

You can authenticate with a bearer token (recommended) — either a workspace-level token (prdm_wsp_...) or a company-level token (prdm_cmp_..., requires workspace_uid to select which workspace requests target). Pass it as api_secret; the SDK detects the token type automatically from its prefix and api_key is not needed:

from paradime import Paradime

paradime = Paradime(
    api_endpoint="API_ENDPOINT",
    api_secret="API_TOKEN",  # e.g. prdm_wsp_... or prdm_cmp_...
    # workspace_uid="WORKSPACE_UID",  # required when using a company-level (prdm_cmp_) token
)

# Use the paradime client to interact with the API

Or with the legacy API key + secret pair:

from paradime import Paradime

paradime = Paradime(
    api_endpoint="API_ENDPOINT", 
    api_key="API_KEY", 
    api_secret="API_SECRET",
)

# Use the paradime client to interact with the API

CLI Usage

For the full specification of the CLI, run:

paradime --help

Generate your API credentials from Paradime workspace settings. Then set the environment variables.

Using a bearer token (recommended):

export PARADIME_API_ENDPOINT="YOUR_API_ENDPOINT"
export PARADIME_API_SECRET="YOUR_API_TOKEN" # e.g. prdm_wsp_... or prdm_cmp_...
export PARADIME_WORKSPACE_UID="YOUR_WORKSPACE_UID" # required when using a company-level (prdm_cmp_) token

Or using the legacy API key + secret pair:

export PARADIME_API_ENDPOINT="YOUR_API_ENDPOINT"
export PARADIME_API_KEY="YOUR_API_KEY"
export PARADIME_API_SECRET="YOUR_API_SECRET

Alternatively, run paradime login to be prompted for either set of credentials, which will be stored locally.

Examples

Find usage examples here to get started with the Paradime Python SDK.

Telemetry

Each API call sends X-PYTHON-VERSION (e.g. 3.11.5) and X-PARADIME-RUNTIME (e.g. github-actions, airflow, paradime-bolt, local) to help Paradime understand how the SDK is being used. Only the presence of well-known CI/platform environment variables is checked — no values are ever transmitted.

To opt out:

export PARADIME_DISABLE_TELEMETRY=true

Metadata

Release files for paradime-io 6.7.0

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

Source distribution (sdist)

Source distribution for paradime-io 6.7.0
File Size Uploaded
paradime_io-6.7.0.tar.gz 276.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for paradime-io 6.7.0
File Interpreter ABI Platform
paradime_io-6.7.0-py3-none-any.whl Python 3 none any Details

Total release size: 503.6 kB

Release files / paradime_io-6.7.0.tar.gz

Download URL paradime_io-6.7.0.tar.gz
Size 276.7 kB
Tags Source
SHA-256 checksum
How to use checksums
bd46bcfe89b706179ce15cf32db8d82c05fc5c67905d1f5151b8363401861976
BLAKE2b-256 checksum
How to use checksums
d398b5a0453391b47b16a580a0d4bdf38a739fb704d476d54d4d0b16d87c78d1
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 Sep 30, 2026.

Transparency log

Release files / paradime_io-6.7.0-py3-none-any.whl

Download URL paradime_io-6.7.0-py3-none-any.whl
Size 226.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
73a2d5120bd819eb78469d2517989b25a96567f09b0abcc638db922824624b32
BLAKE2b-256 checksum
How to use checksums
d70925b030bc1b92196afdf90f5046840b98e189207788c72b983e8dfecf2b03
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 Sep 30, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

6.7.0 This release

2 release files

6.6.0

2 release files

6.4.0

2 release files

6.3.0

2 release files

6.2.0

2 release files

6.1.0

2 release files

6.0.0

2 release files

5.12.0

2 release files

5.11.0

2 release files

5.10.0

2 release files

5.9.0

2 release files

5.8.0

2 release files

5.7.0

2 release files

5.6.0

2 release files

5.5.0

2 release files

5.4.0

2 release files

5.3.0

2 release files

5.2.0

2 release files

5.1.0

2 release files

5.0.0

2 release files

4.19.0

2 release files

4.18.0

2 release files

4.17.1

2 release files

4.17.0

2 release files

4.15.0

2 release files

4.10.3

2 release files

4.10.2

2 release files

4.10.1

2 release files

4.9.0

2 release files

4.8.1

2 release files

4.7.1

2 release files

4.7.0

2 release files

4.6.1

2 release files

4.6.0

2 release files

4.5.0

2 release files

4.4.0

2 release files

4.3.0

2 release files

4.2.0

2 release files

4.1.1

2 release files

4.1.0

2 release files

4.0.0

2 release files

3.0.0

2 release files

2.0.0

2 release files

1.0.0

2 release files

0.1.1

2 release files

0.1.0

2 release files

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