Vesremont developer portal

Vesremont API documentation

The public catalog supports product search, product details, brands, category filters and published reviews. Catalog reads are free and do not require signup, an API key, cookies or buyer consent. Personal carts, favorites, checkout, orders and webhooks are a separate OAuth-authorized branch. API access does not make the products free.

Make the first API call

curl --get 'https://vesremont.com/api/v1/products?per_page=1' --header 'Accept: application/json'

Read items and the returned product id. Search by name or article number with GET https://vesremont.com/api/v1/products?q={url_encoded_query}. Verify the exact model and article number before choosing a result; use the returned internal ID, not a number guessed from the title. Query parameters, filters and pagination are defined by Vesremont OpenAPI.

For an agent that cannot read JSON, the existing /api/v1/products.md?q={url_encoded_query} offers a Markdown alternative. It is not a different product database. Check current prices, availability and orderability in the product response; an inventory count is not a delivery promise.

Read-only sandbox

curl 'https://vesremont.com/oauth/sandbox' --header 'Accept: application/json'

The sandbox returns synthetic read-only data without credentials. It is not a second shop or a full alternate API base URL. It cannot create test carts, place orders, take payment or send data to 1C. See API access and quotas and the complete Vesremont API documentation in Russian.

Vesremont OpenAPI

The official OpenAPI 3.1 JSON specification is the machine-readable REST contract. It describes HTTP methods, paths, parameters, request bodies, response schemas, errors and authentication. It is built from the same operation registry as the running API, not maintained as a separate English schema.

REST base URL: https://vesremont.com/api/v1. Use the exact parameter names and security requirements from the specification. The public catalog requires no credential; an anonymous catalog credential never grants buyer permissions. Documentation examples do not override the live schema or enable a disabled operation.

Vesremont MCP server

The official remote MCP server is https://vesremont.com/mcp, using Streamable HTTP. Connect a compatible MCP client, perform initialize, send notifications/initialized, then request tools/list. Read the current input and output schemas before calling a tool; names and arguments are not inferred from this page.

claude mcp add --transport http vesremont https://vesremont.com/mcp

Use search_products to find candidates and get_product to inspect a returned product ID. Public catalog reads require no API key or OAuth. A successful anonymous handshake or tool list does not authorize private tools: get_cart without a buyer token returns an authorization error.

MCP connection descriptor · Product MCP server card. For documentation questions, use the separate read-only https://vesremont.com/docs/mcp server with search_docs and read_docs. Do not send a buyer token to the documentation server. Product operations stay on the product MCP endpoint.

Connect an existing client

• Claude Code MCP configuration
• Cursor MCP configuration
• Windsurf user-configuration example

Review a configuration before installing it and decide which tools to trust. A connection file or registry listing is not buyer consent. MCP does not require installing a Vesremont REST SDK.

Vesremont SDK documentation and CLI

Official REST clients are published for JavaScript/TypeScript, Python, Ruby and Go. The vesremont CLI is included in the npm package. Use the version-specific package instructions and SDK README for installation, imports and supported commands. These clients use the existing REST API; they do not bypass OAuth or order confirmation.

• JavaScript / TypeScript SDK and CLI: @vesremont_api/api — Node.js 22+.
• Python SDK: vesremont-api — Python 3.10+.
• Ruby SDK: vesremont-api — Ruby 3.3+.
• Go SDK: vesremont-sdk/go — Go 1.22+.

Official SDK source and README · Detailed installation instructions (Russian). The repository contains clients, not the store's server code. Installing a client does not test a purchase; do not place test orders against production.

Vesremont authentication documentation

Choose the permission branch that matches the task. Public catalog reads need no token. The optional anonymous credential is limited to catalog:read for REST and is not a buyer identity. For personal remote operations, obtain explicit buyer consent through OAuth Authorization Code with PKCE S256 and request only the scopes needed by the operation.

Use the correct token resource: REST https://vesremont.com/api/v1 and MCP https://vesremont.com/mcp are different audiences. Do not reuse a REST token as an MCP token or copy a token into a URL. The authorization-server metadata, REST protected-resource metadata and full OAuth walkthrough (Russian) define discovery, scopes, consent, token exchange and revocation.

Remote clients do not forward browser cookies to select a buyer. Browser WebMCP is a different interface: tools are exposed through the current page's document.modelContext and retain the browser session, CSRF and Origin checks. Re-read that context after navigation. A browser session does not replace remote OAuth, and remote OAuth does not replace browser CSRF.

Order confirmation is separate

An OAuth grant does not authorize an unspecified purchase. Read the checkout summary, prepare the order through the selected interface and obtain the buyer's separate confirmation of that concrete order. Use only the issued confirmation credentials and the documented idempotency rules. A saved order is not proof of payment or shipment. Never retry an uncertain order submission with a new idempotency key.

If the task is only to share a product selection, use the existing cart-link handoff instead of requesting personal access. An agent's public GET does not write the buyer's cart; the site performs the protected transfer in the buyer's browser. This English portal does not change any buyer permissions.

Errors, pagination and safe retries

Read each operation's OpenAPI schema for pagination and limits. Follow returned cursors unchanged. Read live rate-limit headers and Retry-After; documentation is not a substitute for the current quota.

• 401: the private operation needs a valid token for the correct resource.
• 403: check scopes, ownership and Origin; do not bypass the refusal.
• 404: verify the product ID or documented URL; do not guess another buyer's identifiers.
• 422: correct parameters against the operation schema before retrying.
• 429: back off according to Retry-After.
• A timeout or 503 during a write is not proof that nothing happened. Reconcile the result and preserve the original idempotency key.

Developer resources and other interfaces

REST, remote MCP, A2A, UCP and browser WebMCP are alternatives, not mandatory onboarding stages. Choose one interface and its documented payload. Do not transplant checkout fields or confirmation tokens between protocols.

• Russian developer portal and full API documentation.
• API Markdown, auth Markdown and capabilities and task routes (Russian).
• Developer documentation index, root documentation index and API catalog.
• Agent manifest and Agent Skills index.
• A2A endpoint: https://vesremont.com/a2a; UCP REST endpoint: https://vesremont.com/ucp/v1. See their discovery documents and the full API guide before using them.

This is documentation, not a live health certificate, independent verification or a promise that a search engine will index the page. Check the actual response before relying on availability.