List all Ozon API sections (Seller + Performance) with method counts.

Use this first to orient yourself in the API. Returns sections grouped by api ('seller' or 'performance'), each with the human-readable section name, the underlying tag, and the number of methods inside.

Full-text search across all Ozon API methods.

Searches over operation_id, path, summary, description, section, and tag using BM25 ranking with field boosting (summary x4, path/op_id x3, description x1). Supports Russian and English queries with stemming.

Args: query: free-text query, e.g. "list of postings" or "финансовые транзакции" section: optional filter — match by section name or tag (case-insensitive substring) api: optional filter — "seller" or "performance" safety: optional filter — "read", "write", or "destructive" limit: max results to return (default 10)

Get a complete description of one Ozon API method.

Returns the method's metadata plus fully-resolved JSON Schema for request and responses. All $ref pointers are inlined; oneOf/anyOf/allOf combinators are preserved verbatim. When knowledge layer is loaded, also includes rate_limit, quirks, examples, and related methods — everything an agent needs to call the method correctly.

Provide either operation_id (preferred) OR path (+ optional http_method).

List all methods inside a section (by section name or tag).

Args: query: section name or tag, e.g. "FinanceAPI", "Финансовые отчёты", "ProductAPI"

Find methods related to a given one (auto-extracted from doc links + workflows).

Returns methods that this operation links to in its description, plus methods that link back to it. Useful for understanding which calls you'll likely need together when integrating a feature.

Args: operation_id: source method max_hops: 1 = direct neighbours, 2 = neighbours of neighbours

List all curated workflows, optionally filtered by category.

Workflows are step-by-step recipes for chaining Ozon API methods into real data pipelines or analytical reports. Use ozon_get_workflow to fetch the full plan for a specific workflow.

Args: category: optional filter — one of "catalog", "orders", "analytics", "health", "pricing", "content", "advertising", "warehouse", "returns", "finance". When provided, only workflows in that category are returned. categories in the response always lists every value present in the catalogue.

Get the full step-by-step plan for one workflow.

Returns ordered steps with operation_ids, pagination/batching/concurrency guidance, recommended DB schema, and known gotchas. Analytical workflows additionally carry interpret (how to read the data), when_to_use (situations the workflow fits) and common_mistakes.

Args: name: workflow name from ozon_list_workflows, e.g. "sync_orders_fbs" or "oos_risk_analysis"

Look up rate limits for a method, section, or the whole API.

Without arguments returns all known limits. With operation_id, returns the most specific limit (per-method overrides per-section overrides global).

NOTE: Many limits in v0.2 are conservative guesses (source: 'guess'). Verify against real Ozon responses before relying on them in production.

Look up Ozon API errors and their solutions.

Without arguments returns all known errors. With code (e.g. "429" or "InvalidArgument") filters by code. With operation_id returns errors specific to that method plus all generic ones.

Get hand-crafted request examples for one method.

Examples are real, validated payloads matching the method's request schema — copy them as starting points for your own calls.

Return metadata about the bundled Ozon swagger snapshots.

Tells the caller which spec version we are shipping, how many methods it contains, when the snapshot was refreshed, and the SHA-256 of the file. Useful for:

• agents that need to decide whether to re-check docs online;

• operators validating that a refresh actually landed;

• bug reports — include this in the issue so reproduction is exact.

Returns {"error": "missing"} when the package was built without swagger_meta.json (pre-v0.6 snapshot).

List all Ozon methods that mention a specific subscription tier.

Useful when an agent wants to know "what extra capabilities do I unlock by upgrading to Premium Plus?" or "which methods will fail without Premium?". Tiers are auto-extracted from method documentation, so this is a hint, not a contract — the actual hard 403 set may differ.

Args: tier: one of UNSPECIFIED, PREMIUM_LITE, PREMIUM, PREMIUM_PLUS, PREMIUM_PRO

Get the current account's subscription tier from /v1/seller/info.

Returns the subscription type, the is_premium flag, plus the list of all Ozon API methods that might require this exact tier. Result is cached per server process; pass refresh=True to bypass the cache. Errors are NEVER cached.

Available only when seller credentials are configured.

Execute a real call against the Ozon API.

SAFETY MODEL — read methods just work; write/destructive methods require explicit confirmation flags. Each method's safety class is visible in ozon_describe_method (safety field).

• safety="read": no flag needed

• safety="write": requires confirm_write=True

• safety="destructive": requires BOTH confirm_write=True AND i_understand_this_modifies_data=True

SUBSCRIPTION GATE — when the method requires a higher tariff than the current cabinet tier, the call is refused locally and no HTTP request is sent. Saves quota on calls that would 403 anyway.

RATE LIMITS — 429 responses are retried up to MAX_RETRIES times honouring Retry-After. Slow endpoints (e.g. /v1/analytics/turnover/ stocks at 1 req/min) are serialised via a per-process semaphore.

On any failure returns a structured OzonError envelope — agents should inspect error_type and decide.

Args: operation_id: e.g. "FinanceAPI_FinanceTransactionListV3" params: request body matching the method's request_schema confirm_write: required when method.safety == "write" or "destructive" i_understand_this_modifies_data: extra confirmation for destructive cabinet_tier: override the cached cabinet tier (e.g. "PREMIUM_PLUS")

Fetch all pages of a paginated Ozon endpoint.

Walks the endpoint's pagination pattern (offset/page/last_id/cursor/ page_token — see knowledge/pagination_patterns.yaml) until the endpoint reports the last page or max_items is reached. Per-page rate limits are still enforced via the same machinery as ozon_call_method.

Args: operation_id: same as ozon_call_method, must support pagination params: request body WITHOUT offset/limit/last_id/cursor — the paginator owns those fields max_items: safety cap, range [1, MAX_FETCH_ALL_ITEMS] cabinet_tier: override the cached cabinet tier

Returns: {"items": [...], "total_fetched": N, "truncated": bool, "pages_fetched": int} on success or a structured OzonError on failure.