[tswfi]

This is a large maintenance pass to bring the package up to date and keep it healthy. It is backwards compatible for the public surface (from procountor.client import Client, the constructor, all method names, properties, and attributes are unchanged) except for a handful of intentional correctness fixes that send different (correct) data on the wire — these are why this is slated for a 3.0.0 release.

No version bump or release is included here; that's a follow-up once this is reviewed.

Tooling / packaging

• Migrated setup.py/setup.cfg/Pipfile/requirements.txt/tox.ini → a single PEP 621 pyproject.toml (hatchling backend), and adopted uv for env/lock management. Removed the dead .pyup.yml and MANIFEST.in.
• Dropped Python 2; now requires Python 3.9+. Refreshed the locked deps so transitive packages (urllib3, etc.) resolve to current, non-vulnerable versions.
• Added the previously empty LICENSE (MIT).
• Added GitHub Actions CI (ruff + mypy + pytest matrix on 3.9–3.13) and modernized the PyPI publish workflow to build with uv.

Tests

• The old suite required live Procountor credentials and hit the network on construction, so it could not run in CI. It now runs fully offline: the live integration tests skip unless PROCOUNTOR_RUN_INTEGRATION=1 (+ credentials), and a new mocked unit-test suite is the CI gate. 67 unit tests pass, 41 integration skip.

Code quality

• Added type hints throughout + a py.typed marker (PEP 561). To keep the types honest, the HTTP transport/auth was extracted into procountor.transport.BaseClient, which ApiMethods now inherits (MRO: Client → ApiMethods → BaseClient).
• Client is now importable from the top level: from procountor import Client.

Generic verbs (the strategic bit)

The Procountor API has ~192 operations; the named helpers cover ~58. Rather than hand-maintain wrappers that drift from the spec, added generic get/post/put/delete verbs so any endpoint is reachable while the client keeps handling auth + token refresh:

client.get("payrolls/salaryslips", salaryPeriodId=123)
client.post("products", json={"name": "Widget"})
client.put("invoices/123/notes", json={"note": "ok"})
client.delete("attachments/42")

request() also gained an explicit json body param (so top-level JSON arrays work). The named helpers were converted to thin wrappers over these verbs (wire-identical) to make it obvious they're just convenience.

Bug fixes (these change what is sent on the wire)

• Request body bug: 8 write methods (update_company, update_user, update_business_partner, create_dimension_item, update_dimension_item, post_payment, payments_direct_bank_transfers, put_products_to_bank_statement) passed the body into request()'s headers arg, so no JSON body was ever sent. Fixed + regression tests.
• get_payments queried /invoices instead of /payments.
• get_invoice_paymentevents sent its args as a GET JSON body; they are query params (previousId, orderById, size, page).
• Leading-slash endpoints (create_dimension_item, update_dimension_item, confirm_invoice) produced double-slash URLs.
• update_dimension now takes a dimensionId and targets PUT /dimensions/{id} (Procountor removed PUT /dimensions around 25.11).
• api_key was stored as a stray 1-tuple; now the documented string (wire-identical).

Deprecations

• pay_invoice and send_one_time_pass now emit DeprecationWarning — their endpoints (/invoices/pay, /users/otp) no longer exist in the current API. They still function.

Ergonomics

• get_bank_statements accepts date/datetime (or strings) for its date-only params. Date normalization deliberately lives in the named wrapper, not the transport — the correct format is per-parameter, so only the method that knows a field's semantics should convert it.

Docs

• README: usage example, generic verbs, and the supported/latest/dated api_version cycle, pointing at https://dev.procountor.com/.
• CONTRIBUTING/README release steps updated for uv + git push --follow-tags.

🤖 Generated with Claude Code