vanda-api 1.0.2__tar.gz → 1.0.3__tar.gz

{vanda_api-1.0.2 → vanda_api-1.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: vanda-api
-Version: 1.0.2
+Version: 1.0.3
 Summary: Official Python SDK for Vanda Analytics Data API
 Project-URL: Homepage, https://gitlab.com/yourusername/vanda-api
 Project-URL: Documentation, https://gitlab.com/yourusername/vanda-api#readme
@@ -288,88 +288,6 @@ client = VandaClient(email="your_email@example.com", password="your_password")
 - `get_timeseries()` - Get timeseries for multiple aggregate id's
 - `get_constituents()` - Get constituents using Vanda identifier
 
-### Positioning Data
-
-Accessed via `client.positioning`.
-
-- `get_timeseries()` - Get positioning timeseries for one or more series
-- `get_latest()` - Get the latest reading per series, with its crowding signal
-- `export_timeseries()` - Export positioning timeseries to file
-- `list_catalog()` - Search the catalog and filter by dimension
-
-```python
-from vanda import VandaClient
-
-with VandaClient(token="YOUR_TOKEN_HERE") as client:
-    catalog = client.positioning.list_catalog(sector="Energy", records_per_page=5)
-    series_label = catalog["data"][0]["identity"]["series_label"]
-
-    data = client.positioning.get_timeseries(
-        series_ids=series_label,
-        start_date="2025-01-01",
-        end_date="2025-12-31",
-    )
-    print(data["count"], data["pagination"])
-```
-
-Responses keep their envelope: alongside `data` you get `count`, `metric`,
-`revision`, `series_ids`, `version` and `pagination`. Use `pagination` to page -
-`records_per_page` defaults to 2000 and is capped by your access tier.
-
-Unlike aggregates, positioning does not accept `normalisation` /
-`normalisation_period`; its values are already z-scores. `transformation` and
-`window` must be passed together.
-
-### Flow Data
-
-Accessed via `client.flow`.
-
-- `get_timeseries()` - Get flow timeseries for one or more series
-- `get_latest()` - Get the latest observation per series
-- `export_timeseries()` - Export flow timeseries to file
-- `list_catalog()` - Search the catalog and filter by dimension
-
-```python
-from vanda import VandaClient
-
-with VandaClient(token="YOUR_TOKEN_HERE") as client:
-    catalog = client.flow.list_catalog(metric="net", records_per_page=5)
-
-    # Catalog entries are keyed by series_label. Read `series` for anything
-    # per-series, and address series by `slug` - `series_id` changes when the
-    # pipeline reloads.
-    slug = catalog["data"][0]["series"][0]["slug"]
-
-    data = client.flow.get_timeseries(
-        series_ids=slug,
-        metrics=["net", "buy"],
-        start_date="2026-01-01",
-        end_date="2026-08-03",
-    )
-    print(data["metrics"], data["unresolved"], data["pagination"])
-```
-
-`series_ids`, `metrics` and `frequency` accept either a comma-separated string
-or a sequence. Identifiers that matched nothing are reported in `unresolved`
-rather than failing the request, so check it before treating a short result as
-complete.
-
-Unlike positioning, flow accepts `normalisation` / `normalisation_period` - each
-must be passed with its partner, as must `transformation` / `window`. A
-transformation has to resolve to exactly one series.
-
-For both services, if the transformation service is unavailable the
-untransformed rows are returned with `transformation.status` set to `"Failure"`
-rather than raising:
-
-```python
-data = client.flow.get_timeseries(
-    series_ids=slug, transformation="moving_avg", window="20"
-)
-if data["transformation"]["status"] == "Failure":
-    print("untransformed:", data["transformation"]["detail"])
-```
-
 ## Examples
 
 See `examples/` directory for complete usage examples.

{vanda_api-1.0.2 → vanda_api-1.0.3}/README.md

@@ -250,88 +250,6 @@ client = VandaClient(email="your_email@example.com", password="your_password")
 - `get_timeseries()` - Get timeseries for multiple aggregate id's
 - `get_constituents()` - Get constituents using Vanda identifier
 
-### Positioning Data
-
-Accessed via `client.positioning`.
-
-- `get_timeseries()` - Get positioning timeseries for one or more series
-- `get_latest()` - Get the latest reading per series, with its crowding signal
-- `export_timeseries()` - Export positioning timeseries to file
-- `list_catalog()` - Search the catalog and filter by dimension
-
-```python
-from vanda import VandaClient
-
-with VandaClient(token="YOUR_TOKEN_HERE") as client:
-    catalog = client.positioning.list_catalog(sector="Energy", records_per_page=5)
-    series_label = catalog["data"][0]["identity"]["series_label"]
-
-    data = client.positioning.get_timeseries(
-        series_ids=series_label,
-        start_date="2025-01-01",
-        end_date="2025-12-31",
-    )
-    print(data["count"], data["pagination"])
-```
-
-Responses keep their envelope: alongside `data` you get `count`, `metric`,
-`revision`, `series_ids`, `version` and `pagination`. Use `pagination` to page -
-`records_per_page` defaults to 2000 and is capped by your access tier.
-
-Unlike aggregates, positioning does not accept `normalisation` /
-`normalisation_period`; its values are already z-scores. `transformation` and
-`window` must be passed together.
-
-### Flow Data
-
-Accessed via `client.flow`.
-
-- `get_timeseries()` - Get flow timeseries for one or more series
-- `get_latest()` - Get the latest observation per series
-- `export_timeseries()` - Export flow timeseries to file
-- `list_catalog()` - Search the catalog and filter by dimension
-
-```python
-from vanda import VandaClient
-
-with VandaClient(token="YOUR_TOKEN_HERE") as client:
-    catalog = client.flow.list_catalog(metric="net", records_per_page=5)
-
-    # Catalog entries are keyed by series_label. Read `series` for anything
-    # per-series, and address series by `slug` - `series_id` changes when the
-    # pipeline reloads.
-    slug = catalog["data"][0]["series"][0]["slug"]
-
-    data = client.flow.get_timeseries(
-        series_ids=slug,
-        metrics=["net", "buy"],
-        start_date="2026-01-01",
-        end_date="2026-08-03",
-    )
-    print(data["metrics"], data["unresolved"], data["pagination"])
-```
-
-`series_ids`, `metrics` and `frequency` accept either a comma-separated string
-or a sequence. Identifiers that matched nothing are reported in `unresolved`
-rather than failing the request, so check it before treating a short result as
-complete.
-
-Unlike positioning, flow accepts `normalisation` / `normalisation_period` - each
-must be passed with its partner, as must `transformation` / `window`. A
-transformation has to resolve to exactly one series.
-
-For both services, if the transformation service is unavailable the
-untransformed rows are returned with `transformation.status` set to `"Failure"`
-rather than raising:
-
-```python
-data = client.flow.get_timeseries(
-    series_ids=slug, transformation="moving_avg", window="20"
-)
-if data["transformation"]["status"] == "Failure":
-    print("untransformed:", data["transformation"]["detail"])
-```
-
 ## Examples
 
 See `examples/` directory for complete usage examples.

{vanda_api-1.0.2 → vanda_api-1.0.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "vanda-api"
-version = "1.0.2"
+version = "1.0.3"
 description = "Official Python SDK for Vanda Analytics Data API"
 readme = "README.md"
 requires-python = ">=3.9"

{vanda_api-1.0.2 → vanda_api-1.0.3}/src/vanda/__init__.py

@@ -10,7 +10,7 @@ from vanda.errors import (
     VandaError,
 )
 
-__version__ = "0.1.0"
+__version__ = "1.0.3"
 
 __all__ = [
     "VandaClient",