Skip to main content

Dime.Scheduler SDK for Python

The official Python SDK for Dime.Scheduler.

Status: alpha. The domain-grouped accessor surface is in place; typed entity models are landing.

Installation

pip install dimescheduler
# or
uv add dimescheduler

Prereleases

Alpha / beta / release-candidate builds (e.g. 0.1.1b0 for 0.1.1-beta.0) ship as PyPI prereleases. To opt into them:

pip install --pre dimescheduler

Quick start

from dimescheduler import DimeSchedulerClient, Environment

with DimeSchedulerClient(api_key="MY_API_KEY", environment=Environment.Sandbox) as client:
    result = client.categories.create({
        "name": "INSTALL",
        "displayName": "Install",
        "color": "#22d3ee",
    })
    if not result.ok:
        raise RuntimeError(result.error)

By default the client targets Environment.Production. Switch to Sandbox or Test for non-prod.

API surface

Every entity hangs off a typed accessor on the client. CRUD-shaped entities expose create / update / delete / get_all:

client.categories.create(category)
client.categories.update(category)
client.categories.delete(category)
result = client.categories.get_all()

Endpoints with required parameters expose them directly:

client.appointments.get(start_date, end_date, resources=["R1", "R2"])
client.notifications.get(page=1, limit=50, sort="createdAt:desc")
client.geocoding.geocode_text("221B Baker Street", "GB")
client.optimization.field_service(request)

Every method returns a Result:

result = client.categories.get_all()
result.ok                 # bool — convenience over response.is_success
result.data               # parsed JSON body on success, else None
result.error              # parsed JSON error body on 4xx/5xx, else None
result.response           # underlying httpx.Response

The accessor names mirror the .NET and JS SDKs 1:1 (with idiomatic snake_case), so cross-language code reads the same.

Development

This package is part of the dime-scheduler/sdk monorepo. From packages/python/:

uv sync --extra dev          # install runtime + dev deps
uv run pytest                # run unit tests
uv run ruff check             # lint
./scripts/codegen.sh          # regenerate typed client from ../../spec/openapi.json

License

MIT

Metadata

Release files for dimescheduler 0.3.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 dimescheduler 0.3.0
File Size Uploaded
dimescheduler-0.3.0.tar.gz 11.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for dimescheduler 0.3.0
File Interpreter ABI Platform
dimescheduler-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 27.1 kB

Release files / dimescheduler-0.3.0.tar.gz

Download URL dimescheduler-0.3.0.tar.gz
Size 11.4 kB
Tags Source
SHA-256 checksum
How to use checksums
efad95e4b5220b208be30ce53e17e2ff11504babc97abc790dc11a2912ad6d9e
BLAKE2b-256 checksum
How to use checksums
af4d0e37a2ee3e2f9686b097ebdb21331d4b9771c7caf43209416a0617c1e42b
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 Oct 10, 2026.

Transparency log

Release files / dimescheduler-0.3.0-py3-none-any.whl

Download URL dimescheduler-0.3.0-py3-none-any.whl
Size 15.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4a43c05a1bb337d9796abf95fa4e2bf1c104cef1911643f88ed861bf9b3be4ec
BLAKE2b-256 checksum
How to use checksums
5a5ad891a31f15c6f2b7b0698398fda982f260015007c8e2dfb457a015bdf964
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 Oct 10, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.0 This release

2 release files

0.2.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