simpro-py
A thin Python client for the SimPro Cloud REST API (v1.0).
from simpro import SimproClient
client = SimproClient("https://yourtenant.simprosuite.com", "YOUR_API_KEY")
for customer in client.customers.iter_all(0):
print(customer["ID"], customer.get("CompanyName") or customer.get("FamilyName"))
The distribution is simpro-py-sdk; the import name is simpro.
Install
pip install simpro-py-sdk
Requires Python 3.12+. The only runtime dependency is httpx.
Authentication
SimPro API keys are bearer tokens — create one in SimPro under Administration > API Keys and pass it with your tenant base URL:
client = SimproClient("https://yourtenant.simprosuite.com", "YOUR_API_KEY")
Every request is sent to {base_url}/api/v1.0/.... If your base_url already
ends with /api/v1.0 it is stripped automatically, so the well-known
doubled-prefix 404 (Invalid route) cannot happen.
Resources
The client ships read-only access to the first-slice resources, one namespace per resource, hung off the client:
| Namespace | Endpoints |
|---|---|
client.companies |
list(*, search=None, modified_since=None, **filters), get(company_id) |
client.customers |
list(company_id, ...), get(company_id, customer_id), iter_all(company_id, **filters) |
client.sites |
list(company_id, ...), get(company_id, site_id), iter_all(company_id, **filters) |
client.jobs |
list(company_id, ...), get(company_id, job_id), iter_all(company_id, **filters) |
client.leads |
list(company_id, ...), get(company_id, lead_id), iter_all(company_id, **filters) — list items are minimal; extra fields come via columns="ID,LeadName,Stage" |
client.quotes |
list(company_id, ...), get(company_id, quote_id), iter_all(company_id, **filters) — same columns projection as leads |
client.webhooks |
list(company_id, ...), get(company_id, webhook_id), iter_all(company_id), create(company_id, data), update(company_id, webhook_id, data), delete(company_id, webhook_id) — webhook subscriptions (setup/webhooks), see below |
company_id is 0 unless your build uses SimPro multi-company.
Notes:
- Single-customer GETs are type-split in SimPro (company vs individual).
client.customers.get(company_id, customer_id)tries the company path first and falls back to individuals, so callers never need the type up front. searchis SimPro's documented match-mode param ("all"/"any") that combines with field filters. Field filters themselves are passed verbatim as extra keyword arguments, e.g.client.customers.list(0, Name="Acme").- All methods return plain dicts/lists — no DTO layer by design.
Pagination
list() fetches a single page (page, per_page, capped at SimPro's maximum
of 250). iter_all() walks every page for you:
for job in client.jobs.iter_all(0):
...
Page continuation follows the SimPro convention: the Result-Pages response
header carries the total page count; if it is absent, the walk stops on a
short page.
Incremental pulls
List endpoints honour the If-Modified-Since watermark. Pass
modified_since=<datetime> and the client formats the header (RFC 1123, UTC)
and maps a 304 Not Modified answer to an empty result:
since = last_sync_run_at # aware datetime; naive values are treated as UTC
new_customers = client.customers.list(0, modified_since=since)
Webhooks
Subscriptions are fully API-managed per build/company — register one yourself instead of asking a tenant admin:
subscription = client.webhooks.create(
0,
{
"Name": "My integration",
"CallbackURL": "https://example.com/webhook/abc123",
"Secret": "shared-secret",
"Events": ["lead.created", "lead.updated", "lead.deleted"],
},
)
webhook_id = subscription["ID"]
client.webhooks.update(0, webhook_id, {"Events": ["lead.created"]})
client.webhooks.delete(0, webhook_id)
The delivery payload is thin — the event name and the record ids only, e.g.
{"ID": "lead.created", "reference": {"companyID": 0, "leadID": 501}} — so
fetch the record from the resource namespace named by the event.
Deliveries are at-least-once and can be paused after repeated failures, with no documented replay API: keep a periodic poll beside the webhook.
Rate limiting
SimPro enforces 10 API calls per second, per build and per IP — a budget
shared across every integration and UI session hitting the build — and
answers over-limit traffic with HTTP 429 (strictly enforced since April
2025).
The client keeps you inside that budget:
client = SimproClient(base_url, api_key) # paced at 9 req/s
client = SimproClient(base_url, api_key, rate_limit=10) # right at the ceiling
client = SimproClient(base_url, api_key, rate_limit=None) # you handle pacing
- Pacing uses a sliding one-second window (default 9 requests/second, just under the ceiling to leave headroom for other traffic on the shared budget) and adds no dependencies.
- The limit is per build, not per client: pass one shared limiter to several clients on the same tenant so they count against a single budget.
from simpro import SlidingWindowRateLimiter
limiter = SlidingWindowRateLimiter(9)
a = SimproClient(base_url, key_a, rate_limiter=limiter)
b = SimproClient(base_url, key_b, rate_limiter=limiter)
- When SimPro still answers
429(other integrations can consume the shared budget), the client retries automatically — up tomax_retriestimes (default 3), honouringRetry-Afterwhen present, otherwise exponential backoff (1s, doubling, capped at 30s). Setmax_retries=0to disable retrying.
Errors
All failures raise a subclass of SimproError:
| Exception | HTTP status |
|---|---|
SimproAuthError |
401, 403 |
SimproNotFound |
404 |
SimproValidationError |
422 (.details holds the raw error list) |
SimproRateLimitError |
429 after retries exhausted (.retry_after holds the parsed header, when sent) |
SimproError |
anything else, including transport failures |
SimPro 422 bodies are normally {"errors": [{"path", "message", "value"}, ...]}
but the errors key may be absent — both shapes are handled, and
SimproValidationError.details is always a list.
Deliberate omissions
- No retry on transport errors — only
429is retried automatically (see Rate limiting); connection resets and timeouts remain the caller's job. - No caching.
- Writes are limited to webhook subscriptions —
create/update/deleteonclient.webhooks; every other namespace is read-only. - No DTO layer — responses are plain JSON dicts, so SDK releases never lag the API.
Lineage
This package is a clean rewrite of limx0/simpro-py
(MIT), which wrapped SimPro's legacy on-prem JSON-RPC API. The rewrite targets
the SimPro Cloud REST API and shares no code with the original; the MIT
licence and lineage are retained with thanks.
Development
uv sync
uv run pytest -q
uv run ruff check . && uv run ruff format --check .
uv run mypy
Licence
MIT — see LICENCE.txt.
Metadata
Release files for simpro-py-sdk 0.3.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 | |
|---|---|---|---|---|
| simpro_py_sdk-0.3.0.tar.gz | 54.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| simpro_py_sdk-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 73.5 kB
Release files / simpro_py_sdk-0.3.0.tar.gz
| Download URL | simpro_py_sdk-0.3.0.tar.gz |
|---|---|
| Size | 54.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ac3568b9d821c0886245f537c77ccc245af7520772db9ebb1bf69842492cfa9
|
|
BLAKE2b-256 checksum How to use checksums |
3720c71279f40b423dce15ef2644fdd9b12468fcf0220b01f264aa0f5f05c707
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 25, 2026.
Transparency logRelease files / simpro_py_sdk-0.3.0-py3-none-any.whl
| Download URL | simpro_py_sdk-0.3.0-py3-none-any.whl |
|---|---|
| Size | 19.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d30f20ce1ccfc1c7b91354ba0e2a37a82480ee8ebe6086ad6b934d1196f8743d
|
|
BLAKE2b-256 checksum How to use checksums |
563479955bdbfca5f2a352ce5fc2a26f836335bc4b152a1cff8b5a02c2d247f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 25, 2026.
Transparency logSecurity for simpro-py-sdk 0.3.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for simpro_py_sdk-0.3.0.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 25, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.