easyvista-python-client 0.1.0__tar.gz

easyvista_python_client-0.1.0/.gitignore

@@ -0,0 +1,43 @@
+secrets/*
+secrets/
+.env
+.env.*
+__pycache__/
+*.py[cod]
+.venv/
+venv/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+dist/
+build/
+*.egg-info/
+
+# Sphinx build output
+docs/_build/
+
+# Local agent/tooling state. These must be listed in THIS file specifically:
+# hatchling reads only the root .gitignore when assembling the sdist, and
+# ignores both nested .gitignore files and the user's global ignore file.
+.claude/
+.superpowers/
+
+# Internal planning docs. Mirrors the sister package (glpi_python_client
+# gitignores docs/superpowers/* too). Kept on disk for local use; never
+# published, because they narrate the private preprod instance.
+docs/superpowers/
+
+# Instance-specific artifacts generated from, or describing, a private
+# EasyVista instance. Useful locally, not publishable: they carry the
+# instance host/account, the end customer's org structure, and a map of
+# that instance's bespoke customization.
+docs/API_Info.md
+docs/easyvista-test-profile-blocked-operations.md
+docs/easyvista-field-inventory.md
+
+# One-off API-exploration scripts. They hardcode a real client's records and
+# print real employees' names and e-mail addresses. Kept on disk so they stay
+# usable locally; never published.
+scripts/probe_*.py

easyvista_python_client-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,79 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.16.0
+    hooks:
+      - id: ruff-check
+      - id: ruff-format
+  - repo: https://github.com/pre-commit/mirrors-mypy
+    rev: v2.3.0
+    hooks:
+      - id: mypy
+        additional_dependencies: ["pydantic>=2.8", "httpx", "tenacity"]
+        # Must mirror [tool.mypy] exclude in pyproject.toml. pre-commit passes
+        # filenames explicitly, and mypy ignores its own `exclude` for files named
+        # on the command line -- so this regex is the ONLY thing keeping the hook
+        # in step with the project's type-checking policy. `integration_tests/`
+        # needs its own alternative: pyproject's bare `tests/` matches it as a
+        # substring, but the anchored `(^|/)tests/` here does not.
+        exclude: (^|/)tests/|(^|/)testing/|^integration_tests/
+  - repo: local
+    hooks:
+      # Fails on a _sync/ tree left stale by an edit to _async/. Runs at
+      # commit time rather than pre-push so the generated tree is never
+      # committed out of step with its source. `language: python` (not
+      # `system`) so pre-commit builds this hook its own managed venv --
+      # bootstrapped from whatever interpreter ran pre-commit itself, never
+      # by searching PATH for a bare `python` -- so it is unaffected by a
+      # `python` on PATH that isn't this project's interpreter (as on
+      # Windows, where it commonly resolves to the Microsoft Store stub).
+      # unasync_build.py imports only the stdlib plus `unasync`, so that is
+      # the hook's entire additional_dependencies list.
+      #
+      # Both pins below are exact, not ranges: this hook is a byte-equality
+      # gate between _async/ and the checked-in _sync/, and unasync (via
+      # tokenize_rt, which actually re-tokenizes and reconstructs the source
+      # bytes) is the generator that equality is measured against. A patch
+      # release of either that changes whitespace reconstruction would fail
+      # this hook on an untouched commit with a misleading "out of date"
+      # message, and the obvious "fix" -- regenerate -- produces a large
+      # unreviewed diff. Bump these deliberately, in their own commit, with
+      # --check re-run by hand; do not relax back to a range.
+      - id: unasync-check
+        name: generated sync tree is up to date
+        entry: python unasync_build.py --check
+        language: python
+        additional_dependencies: ["unasync==0.6.0", "tokenize-rt==6.2.0"]
+        types: [python]
+        pass_filenames: false
+      # `_sync/` as a whole is excluded from ruff (see [tool.ruff]
+      # extend-exclude in pyproject.toml) because it is generated and the
+      # formatter would fight the generator forever. But two files under it
+      # are hand-written on both sides -- unasync_build.HAND_WRITTEN -- and
+      # the directory-wide exclusion silently skips them too, so nothing has
+      # ever formatted or linted them. This runs ruff on exactly those paths,
+      # read from HAND_WRITTEN itself so it stays correct if that set
+      # changes. Also `language: python` for the reason given above.
+      # `ruff==0.16.0` is pinned to match the `astral-sh/ruff-pre-commit`
+      # `rev` above exactly, so the two hand-written twins are never
+      # formatted one way by that hook's ruff and another way by this one --
+      # they just never overlap in file scope, but they use one ruff.
+      #
+      # `unasync`/`tokenize-rt` are exact-pinned here too, matching the
+      # unasync-check hook above -- this script only imports unasync_build
+      # for HAND_WRITTEN/SYNC_DIR and never calls _generate()/_check(), so it
+      # is not itself a byte-equality gate, but it still needs unasync_build's
+      # `import unasync` to succeed, and there is no reason to let a second,
+      # independently-resolved copy of either package float in this repo's
+      # hooks.
+      - id: hand-written-sync-lint
+        name: format and lint the hand-written _sync/ twins
+        entry: python scripts/lint_hand_written_sync.py
+        language: python
+        additional_dependencies:
+          ["unasync==0.6.0", "tokenize-rt==6.2.0", "ruff==0.16.0"]
+        # Mirrors unasync_build.HAND_WRITTEN by hand; there is no way to read
+        # that set before pre-commit decides which files to run hooks on, so
+        # keep this pattern in step with HAND_WRITTEN if it ever gains a
+        # third entry.
+        files: ^easyvista_python_client/_sync/(_concurrency\.py|tests/test_concurrency\.py)$
+        pass_filenames: false

easyvista_python_client-0.1.0/.readthedocs.yaml

@@ -0,0 +1,17 @@
+version: 2
+
+build:
+  os: ubuntu-24.04
+  tools:
+    python: "3.12"
+
+sphinx:
+  configuration: docs/conf.py
+  fail_on_warning: true
+
+python:
+  install:
+    - method: pip
+      path: .
+      extra_requirements:
+        - docs

easyvista_python_client-0.1.0/CHANGELOG.md

@@ -0,0 +1,192 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+While the package is pre-1.0, breaking changes may land between minor versions;
+a deprecation policy will follow the 1.0 release.
+
+## [Unreleased]
+
+### Added
+
+- Python 3.13 and 3.14 are now tested and declared supported (classifiers, and
+  the CI/release matrices, now span 3.10--3.14). No code changed: the suite
+  passes unmodified on both, with the same statement count and coverage as on
+  3.10, and the generated `_sync/` tree regenerates byte-identically under each
+  interpreter's tokenizer.
+- `.github/workflows/release.yml`: releases are built and published to PyPI by
+  CI when a GitHub release is published, using Trusted Publishing (no API token
+  in the repository). The workflow re-runs the test matrix and the quality gates,
+  refuses to build when the release tag, `pyproject.toml` and
+  `easyvista_python_client.__version__` disagree, runs `twine check`, and then
+  triggers a Read the Docs build for the release. `workflow_dispatch` rehearses
+  everything except the upload. See `docs/publishing.rst`.
+- `skills/`: eight Agent Skills covering client setup, search syntax, tickets,
+  ticket actions, documents, assets, the directory and reporting/context, with
+  an index in `skills/README.md`. Shipped in the source distribution, not in
+  the wheel.
+- `scripts/tests/test_skills_contract.py`: checks every skill's frontmatter and
+  code snippets against the real public API, so a rename fails CI.
+- Public `filters.py`: `ev_equals_filter`, `ev_in_filter`, `escape_ev_value`, and
+  `is_safe_ev_value` for building EasyVista `search` expressions safely.
+- `Request` now declares fields that were previously reachable only as untyped
+  `extra="allow"` data — each verified present on live single-ticket GETs:
+  `title`, `request_id`, `external_reference`, `sd_catalog_id`, `urgency_id`,
+  `impact_id`, `severity_id`, `request_origin_id`, `department_id`,
+  `location_id`, `requestor_id`, `recipient_id`, `owner_id`, `submit_date_ut`,
+  and `last_update`.
+- `RequestUpdate.title` — a ticket's title can now be changed after creation
+  (`PUT /requests/{rfc}`), not only set at create time.
+- `EasyvistaClient.download_document` / `AsyncEasyvistaClient.download_document`
+  fetch an attachment's bytes. An absolute download URL is followed only when
+  its scheme and host match the configured `server`: every request carries the
+  instance's Bearer token, so a URL naming another host is refused rather than
+  followed.
+- `Request` now declares the official time-limit fields as typed attributes:
+  `creation_date_ut`, `max_resolution_date_ut`, `expected_date_ut`,
+  `end_date_ut`, `sla_id` and `time_used_to_solve_request`. As with the existing
+  timestamps, they are verified *returned* and no datetime parsing is claimed.
+  The instance-specific `E_GTR_*` / `E_GTI_*` family stays undeclared and
+  reachable through `classify_fields().custom`.
+- `EasyvistaClient.get_action` / `AsyncEasyvistaClient.get_action` fetch a single
+  action. The item-level record carries Memo links that `list_actions` omits —
+  including `DESCRIPTION`, which is where an action's note text actually lives.
+- `Action.description` and `Action.href`, plus an `action_id` derived from `href`
+  when the API omits it. The derivation is deliberately narrow: it uses `href`'s
+  trailing segment only when that segment is numeric, which is the case for an
+  item-level `GET actions/{id}`, and it never overwrites an `ACTION_ID` the API
+  did send. It does **not** fire for a create response — `POST
+  requests/{rfc}/actions` echoes an HREF naming the **parent request**, so the
+  tail is an RFC number rather than an id. A created action's id is therefore not
+  recoverable from its create response at all; diff `list_actions` across the
+  create to identify it (verified live).
+- `get_ticket_context(..., resolve_action_bodies=True)` resolves each action's
+  note text. Pass `False` to skip it — it costs two extra requests per action.
+
+### Removed
+
+- **Breaking:** `PostRequest.catalog_guid` and `Request.catalog_guid` are gone.
+  `CATALOG_GUID` is absent from every sampled live ticket (0/25 single-ticket
+  GETs), from the documented create body, and from the vendor field inventory —
+  it could never populate. `PostRequest(catalog_guid=...)` previously validated
+  and was sent to the API; it now raises (`extra="forbid"`) instead of being
+  silently accepted. Use `catalog_code` to name a catalog on create.
+
+### Fixed
+
+- `find_departments` and `list_actions` interpolated caller values into a `search` expression
+  unescaped. Because `,` is an EasyVista combinator, a crafted value could silently widen the
+  result set (verified live: a department lookup returned 2 records instead of 1). Both now
+  validate the value.
+- `TicketContext.to_markdown` rendered every action with an empty body. It read
+  the text from `Action.comment`, but `COMMENT` is a distinct field that never
+  carries it; the note supplied as `PostAction.description` comes back through
+  the action's `DESCRIPTION` Memo, which is reachable only via an item-level
+  `GET actions/{id}`. Verified against a live instance.
+- **Every mapped exception's message no longer interpolates the raw HTTP response
+  body.** For a body this client does not recognize (an nginx or WAF HTML page, a
+  plain-text 503, any unmodelled shape), the message previously ended with that
+  body's literal text — which then surfaced verbatim wherever the exception was
+  rendered (`str(exc)`, a traceback, a test runner's failure summary), regardless
+  of what the body actually contained. The message now reports only the byte
+  count. **Added:** `EasyvistaError.body` (`bytes | None`) carries the raw
+  response body, so the content dropped from the message is not lost — it is the
+  only way left to retrieve an unrecognized body. `.status_code`, `.ev_code` and
+  `.ev_message` are unaffected: a *recognized* EasyVista error body (one with a
+  parseable `error`/`error_code` shape) reads exactly as it did before.
+
+### Changed
+
+- `AsyncEasyvistaClient.get_ticket_context` and `get_department_context` now issue their
+  independent sub-requests **concurrently** instead of one after another. The async client
+  previously awaited every call in sequence, so it was no faster than the synchronous one
+  (measured against a live instance on a ticket with 19 actions: 14.65s async, 13.44s sync,
+  5.31s after this change). Same requests, same results, same degradation on 403/404 — only
+  the issue order changed. Peak in-flight is 4 sub-resource requests then at most 8
+  concurrent action-body resolutions for a ticket, and 7 branches for a department.
+  Two deltas worth knowing: on a **failing** bundle the siblings already in flight are
+  awaited before the error propagates, so an error path can issue more requests than it did
+  before (bounded by the fan-out width, and all of them reads); and when two branches fail,
+  the exception raised is the first in source order — the one the sequential version would
+  have raised — rather than whichever failed soonest. `create_tickets` stays deliberately
+  sequential: those are writes, and a mid-batch failure must leave a knowable prefix.
+- `TicketContext.to_markdown()` now titles a lone narrative block `## Description` whichever
+  memo it arrived in. A ticket's body does not always live in `DESCRIPTION` — on the verified
+  instance that memo is unused and `COMMENT` carries the body (and `RequestUpdate.description`
+  writes `COMMENT` on any instance), so the rendered document titled a ticket's main text
+  "Comment", which misleads an LLM or a RAG chunker splitting on headings. The renderer no longer
+  assumes either mapping: when only one memo has text it is the body and is titled
+  `## Description`; when both do, the distinction is real and each keeps its own heading, byte
+  identical to before. An instance that populates `DESCRIPTION` is unaffected. The
+  `TicketContext.description` / `.comment` attributes are unchanged and still name their
+  source memo.
+- **Documentation of observed behaviour, not a code change:** a `description` supplied to
+  `PostRequest` at create time is not readable back through either the `DESCRIPTION` or the
+  `COMMENT` Memo on the verified instance. `RequestUpdate.description` writes the ticket's
+  `COMMENT` Memo, not `DESCRIPTION` — verified live (0/15 sampled tickets, portal-created
+  included, have a non-empty `DESCRIPTION`; 15/15 have a non-empty `COMMENT`). Read the body
+  text back with `TicketContext.comment` (or `resolve_memo("requests/{rfc}/comment")`
+  directly), not `Request.description`. Both fields stay as they are; nothing was renamed.
+- **Documentation correction:** the `search` operator `~` was documented as "contains". It is
+  **exact match**, identical to `:` — verified against a live instance. Examples implying
+  substring matching (`ASSET_TAG~LAPTOP`) were wrong and have been replaced. The unverified
+  `!~` / `!` / `is_null` / `is_not_null` operators are no longer documented as fact.
+- **Documentation correction:** the README's and user guide's tutorial examples filtered with
+  `ev_equals_filter("STATUS_EN", "Open")`. `STATUS_EN` is a sub-key of the nested `STATUS`
+  object, not a top-level column, so EasyVista silently ignored the condition and every example
+  returned *all* tickets, not just open ones. This was a documentation defect, not a library bug
+  — the library does not special-case field names, so nothing in the shipped code was broken.
+  Replaced with `ev_equals_filter("STATUS_ID", 3)` throughout, and the user guide now documents
+  which returned fields are actually searchable and the third (HTTP 590 type-mismatch) search
+  outcome.
+- `Request.status_id`, along with the model's other numeric identity/classification fields, now
+  uses an `OptionalInt` type that tolerates the API's `""` for an absent numeric; `status_id`
+  previously raised a validation error on that value.
+- `get_department_context` now raises `ValueError` for a blank or unrenderable `department_id`
+  rather than building a malformed search (defence in depth; not a demonstrated exploitable path).
+- The synchronous client is now **generated** from the asynchronous one with
+  `unasync`. `easyvista_python_client/_async/` is the only hand-written client
+  source; `_sync/` is produced by `python unasync_build.py`, checked in, and
+  verified in CI. Sync/async parity is enforced by a build gate instead of by
+  convention.
+- **Internal module paths moved.** `easyvista_python_client.client` and
+  `easyvista_python_client.async_client` no longer exist. Import from the
+  package root instead — `from easyvista_python_client import EasyvistaClient,
+  AsyncEasyvistaClient` — which is unchanged and has always been the supported
+  surface. `easyvista_python_client._transport.RequestSpec` is also unchanged.
+- `EasyvistaClient.ticket_statistics` now collects its page of tickets into a
+  list before aggregating, rather than streaming the iterator. No behavioural
+  difference at the default `max_records=100`; at `max_records=None` peak
+  memory is now proportional to the result set.
+- `EasyvistaClient.get_ticket_context` now lists documents before resolving
+  action bodies, rather than after. The same requests are issued and the
+  result is identical; only their order on the wire changed.
+
+## [0.1.0] - 2026-07-15
+
+Initial public release.
+
+### Added
+
+- Synchronous `EasyvistaClient` and asynchronous `AsyncEasyvistaClient` over the
+  EasyVista Service Manager REST API, with Bearer or HTTP Basic authentication
+  and `EasyvistaConfig.from_env()`.
+- Tickets (requests): create, batch create, get, update, search, close, and
+  offset-following `iter_tickets()` pagination.
+- Assets, actions, and documents (base64-in-JSON upload, attachment listing).
+- Departments and employees directory, including fuzzy `find_departments()`
+  and department context.
+- `TicketContext.get_ticket_context()` with an href-free `to_markdown()`
+  renderer.
+- Reporting helpers: `count_tickets`, `ticket_statistics`, and the pure
+  `aggregate_tickets()` core.
+- Reference normalization (`Reference`, `localized_label`) and a generic field
+  model (`FieldClassification`) separating official from custom `e_*` fields.
+- Typed exception hierarchy rooted at `EasyvistaError`, carrying the EasyVista
+  status/error code, with non-retryable validation errors (HTTP 590, code 2013).
+- `py.typed` marker — the package ships inline type information.
+
+[Unreleased]: https://github.com/baraline/easyvista_python_client/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/baraline/easyvista_python_client/releases/tag/v0.1.0

easyvista_python_client-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,94 @@
+# Contributing
+
+Thank you for improving `easyvista-python-client`.
+
+The full guide lives in [docs/development.rst](docs/development.rst) (published as
+the [development guide](https://easyvista-python-client.readthedocs.io/en/latest/development.html));
+this page is the short version.
+
+## Development Setup
+
+```bash
+python -m venv .venv
+.venv\Scripts\activate
+python -m pip install -e ".[dev]"
+python -m pre_commit install
+python -m pre_commit run --all-files
+python -m pytest -m "not integration"
+```
+
+## Quality Checks
+
+Run these before opening a pull request:
+
+```bash
+python -m pre_commit run --all-files
+python -m pytest -m "not integration"
+python -m ruff check .
+python -m mypy easyvista_python_client
+```
+
+Coverage is enforced at 95% and `--cov` is always on via `addopts`, so a
+single-file run needs `--no-cov` to avoid a spurious under-coverage failure:
+
+```bash
+python -m pytest easyvista_python_client/tests/test_client.py --no-cov
+```
+
+## Documentation build
+
+```bash
+python -m sphinx -W --keep-going -b html docs docs/_build/html
+```
+
+## Live integration tests
+
+`integration_tests/` lives at the repository root, apart from the unit tests
+inside the package, because it calls a **real EasyVista instance that you
+supply**. It never runs in CI — CI runs `pytest -m "not integration"`.
+
+Credentials come from `EASYVISTA_TEST_*` environment variables, falling back to
+files under `secrets/` (both gitignored). With none configured the suite skips
+cleanly, so `pytest` on a fresh checkout is offline and green.
+
+> **These tests are not read-only.** They create tickets and close them in
+> teardown. Once your credentials are present they run as part of a plain
+> `pytest` — use `pytest -m "not integration"` for a unit-only run. Point them at
+> a preprod or test instance, never production.
+
+Never commit an instance host, account id, or token — see the note below.
+
+## Design Guidelines
+
+- Keep API calls behind `EasyvistaClient` / `AsyncEasyvistaClient` methods. The
+  two surfaces are hand-maintained in parallel: a method added to one must be
+  added to the other with the same name and signature.
+- Prefer declaring a new documented endpoint as a resource descriptor plus a
+  model over hand-writing a builder.
+- Prefer field-validated Pydantic models for request and response payloads.
+- Keep instance-specific values out of the library, the docs, and the tests.
+  Catalog codes, department/urgency/impact ids, and status GUIDs vary per
+  EasyVista instance; use obviously synthetic placeholders in examples and
+  fixtures rather than values copied from a real instance.
+- Add tests for payload serialization and response normalization when adding
+  endpoints. Unit tests live beside the code: one test module per source
+  module, in that package's `tests/` directory (`models/request.py` is covered
+  by `models/tests/test_request.py`). Tests that span several modules, and any
+  shared fixture, belong in `easyvista_python_client/testing/`. Neither
+  directory ships in the wheel or the sdist.
+- "One test module per source module" is a ceiling, not a floor: a source
+  module whose behaviour is fully exercised through a caller's tests (for
+  example a model asserted only via the resource and client tests that build
+  it) does not need its own near-empty test file. Check coverage before adding
+  one.
+
+## Agent skills
+
+A change to the public API must update the affected `skills/*/SKILL.md`, and a
+release that bumps `__version__` must bump every skill's `metadata.version`.
+`scripts/tests/test_skills_contract.py` is the gate: it parses every `SKILL.md`
+and asserts each symbol, client method, keyword argument and model field the
+skill names still exists on the public surface. Run it with
+`pytest scripts/tests/test_skills_contract.py --no-cov` (see the coverage note
+above — a single-file run without `--no-cov` fails the 95% gate even when
+every test passes).

easyvista_python_client-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 easyvista-python-client contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

easyvista_python_client-0.1.0/PKG-INFO

@@ -0,0 +1,178 @@
+Metadata-Version: 2.4
+Name: easyvista-python-client
+Version: 0.1.0
+Summary: Typed Python client for the EasyVista Service Manager REST API
+Project-URL: Homepage, https://github.com/baraline/easyvista_python_client
+Project-URL: Documentation, https://easyvista-python-client.readthedocs.io/en/latest/
+Project-URL: Issues, https://github.com/baraline/easyvista_python_client/issues
+Project-URL: Source, https://github.com/baraline/easyvista_python_client
+Author: easyvista-python-client contributors
+License-Expression: MIT
+License-File: LICENSE
+Keywords: api,client,easyvista,itsm,rest,service-manager
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Internet :: WWW/HTTP
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: httpx>=0.27
+Requires-Dist: pydantic>=2.8
+Requires-Dist: tenacity>=8.2
+Requires-Dist: typing-extensions>=4.7; python_version < '3.11'
+Provides-Extra: dev
+Requires-Dist: build>=1.2; extra == 'dev'
+Requires-Dist: mypy>=1.11; extra == 'dev'
+Requires-Dist: numpydoc>=1.8; extra == 'dev'
+Requires-Dist: pre-commit>=4.0; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest-cov>=5.0; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: respx>=0.21; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Requires-Dist: sphinx-rtd-theme>=2.0; extra == 'dev'
+Requires-Dist: sphinx<8.2,>=7.2; extra == 'dev'
+Requires-Dist: tokenize-rt==6.2.0; extra == 'dev'
+Requires-Dist: tomli>=2.0; (python_version < '3.11') and extra == 'dev'
+Requires-Dist: twine>=5.1; extra == 'dev'
+Requires-Dist: unasync==0.6.0; extra == 'dev'
+Requires-Dist: vulture>=2.11; extra == 'dev'
+Provides-Extra: docs
+Requires-Dist: numpydoc>=1.8; extra == 'docs'
+Requires-Dist: sphinx-rtd-theme>=2.0; extra == 'docs'
+Requires-Dist: sphinx<8.2,>=7.2; extra == 'docs'
+Requires-Dist: tomli>=2.0; (python_version < '3.11') and extra == 'docs'
+Description-Content-Type: text/markdown
+
+# easyvista-python-client
+
+Typed Python client for the EasyVista Service Manager REST API. Sync + async,
+Pydantic models, Bearer or Basic auth.
+
+While the package is preparing for 1.0, alot of potential breaking change might happen between versions. A deprecation policy will be put in place once 1.0 is out and the package have been stabilized.
+
+## Documentation
+
+Full documentation: https://easyvista-python-client.readthedocs.io/
+
+Build it locally with `pip install -e ".[docs]"` then
+`sphinx-build -b html -W docs docs/_build/html`.
+
+## Install
+
+```bash
+pip install easyvista-python-client
+```
+
+## Usage (sync)
+
+```python
+from easyvista_python_client import (
+    EasyvistaClient,
+    EasyvistaConfig,
+    PostRequest,
+    ev_equals_filter,
+)
+
+config = EasyvistaConfig(server="https://my.easyvista.com", account="12345", token="...")
+with EasyvistaClient(config) as client:
+    # catalog_code, the *_id values and the close status_guid are instance-specific.
+    ticket = client.create_ticket(
+        PostRequest(
+            catalog_code="INC_STANDARD",
+            title="Printer down",
+            description="The 3rd-floor printer is offline",
+            origin=7,
+            department_id=9,
+            urgency_id=8,
+            impact_id=28,
+        )
+    )
+    fetched = client.get_ticket(ticket.rfc_number)
+    open_status = ev_equals_filter("STATUS_ID", 3)
+    results = client.search_tickets(search=open_status, max_rows=50)
+
+    # page through everything with the iterator (follows the API's offset paging)
+    for t in client.iter_tickets(search=open_status, page_size=100, max_records=1000):
+        ...  # async: `async for t in client.iter_tickets(...)`
+
+    # close it with your instance's "closed" status GUID
+    client.close_ticket(
+        ticket.rfc_number,
+        status_guid="{00000000-0000-0000-0000-000000000000}",
+        delete_actions=1,
+        comment="Resolved",
+    )
+```
+
+> Minimum fields for a create are catalog-specific (server-side). `catalog_code` + `title`
+> work for incident catalogs; a missing mandatory field raises `EasyvistaValidationError`
+> (HTTP 590, code 2013) — it is not retried.
+
+## Assets and documents
+
+```python
+from pathlib import Path
+from easyvista_python_client import (
+    EasyvistaClient,
+    EasyvistaConfig,
+    PostAsset,
+    ev_equals_filter,
+)
+
+with EasyvistaClient(EasyvistaConfig.from_env()) as client:
+    asset = client.create_asset(PostAsset(catalog_id=3153, asset_tag="LAPTOP-001"))
+    tag_filter = ev_equals_filter("ASSET_TAG", "LAPTOP-001")
+    found = client.search_assets(search=tag_filter, max_rows=50)
+
+    # attach a file to a ticket (uploaded as base64 inside the JSON body)
+    pdf = Path("report.pdf")
+    client.add_document("I240101_0001", filename=pdf.name, content=pdf.read_bytes())
+    attachments = client.list_documents("I240101_0001")
+```
+
+## Usage (async)
+
+```python
+from easyvista_python_client import AsyncEasyvistaClient, EasyvistaConfig
+
+async with AsyncEasyvistaClient(EasyvistaConfig.from_env()) as client:
+    ticket = await client.get_ticket("I240101_0001")
+```
+
+## Configuration via environment
+
+Set `EASYVISTA_URL` (or `EASYVISTA_SERVER`), `EASYVISTA_ACCOUNT`, and either
+`EASYVISTA_TOKEN` / `EASYVISTA_TOKEN_FILE` or `EASYVISTA_LOGIN` + `EASYVISTA_PASSWORD`,
+then call `EasyvistaConfig.from_env()`.
+
+## Agent skills
+
+`skills/` holds Agent Skills for driving this client from an AI agent — one per
+domain (client setup, search syntax, tickets, actions, documents, assets,
+directory, reporting and context). Each is a directory with a `SKILL.md`
+following the Agent Skills specification; see [skills/README.md](skills/README.md)
+for the index.
+
+They are source-tree material: present in the git repository and the source
+distribution, absent from the installed wheel.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and quality checks.
+
+## License
+
+MIT — see [LICENSE](LICENSE).
+
+## Sponsoring
+
+The development of this package is indirectly supported by
+[Novahé](https://www.novahe.fr/) & [Constellation](https://www.constellation.fr/).