Stay up-to-date with the latest changes and improvements to the Eshop-rychle API
Subscribe:
Added customerCreate, customerChange and customerDelete webhooks. Active API users are notified whenever a registered customer is created, their registration data changes (name, phone, billing details, …), or they are deleted — from the admin, the storefront account, the API or imports. Notifications are batched per request and de-duplicated, so a single call can carry multiple customers. The payload contains only customer IDs; fetch the current data via GET /api-engine/customers/{id} (a deleted customer returns 404). Each webhook fires only if the API access is allowed to read customers.
Shops now expose a neutral, versioned frontend contract (window.dataLayer[0].eshop + events: pageVisit, loggedUser, cartUpdated, orderSubmitted, cookieConsent). Partners hook their own JS loader onto it via a CustomCode add-on — no per-partner code on our side. Consent is handled by the partner loader itself through a neutral runtime consent signal. See the Frontend dataLayer page for the full schema, events and versioning.
Outgoing webhooks can now be signed so you can verify they really came from us and were not altered in transit. Generate a signing key in the API administration (section „Zabezpečení webhooků") and every webhook is then sent with the X-Webhook-Signature header (sha256=<hex>, an HMAC-SHA256 of timestamp + "." + raw body) and X-Webhook-Timestamp. Signing is opt-in — without a key webhooks are sent unsigned as before — and the key can be rotated without downtime.
Added the packageOpenInstructions webhook. Whenever a shop admin opens the installation instructions of an add-on, active API users receive a system webhook notification.
The admin login screen and the in-app header now clearly mark non-production environments, so it is obvious at a glance that you are working on the developer interface and not on production. The production interface stays unmarked.
Added the POST /basket-price-quotes endpoint, letting configurator add-ons sell a catalog product at a custom, calculated price (e.g. made-to-measure goods priced by the shopper's dimensions). The add-on computes the price on its own backend and registers a one-time, per-unit price quote server-to-server, receiving an opaque single-use token. Its in-browser widget then passes that token (quoteToken) to the standard add-to-basket request to insert the product at the quoted price. The price lives server-side, so the browser never carries the amount and it cannot be tampered with; all standard cart discounts still apply on top, and the shopper picks the quantity as for any product. An optional cart note and image (POST /basket-price-quote-images) can be attached for the merchant to see on the order.
Added productCreate, productChange and productDelete webhooks. Active API users are notified whenever a product or any of its related data changes — from the admin, the API, imports or orders. Notifications are batched per request and de-duplicated, so a single call can carry multiple products. The payload contains only product IDs (and the affected variant IDs); fetch the current data via GET /api-engine/products/{id}. Each webhook fires only if the API access is allowed to read products.
Added cleanup order endpoints that link a custom code to an API package. When the package is deactivated, any custom codes with an active cleanup order are automatically removed from the e-shop. Without a cleanup order, custom codes created via API remain on the e-shop after deactivation — partners are expected to register a cleanup order for every custom code they distribute.
Added shopOwnerChange webhook. When the shop owner changes, all active API users receive a webhook notification with the new owner email, the website URL and the time of origin.
Discount coupons now expose created and changed timestamps. The collection endpoint accepts a changed date filter (e.g. changed[after]) so clients can fetch incremental updates instead of downloading the full list.
Order states marked as deleted are no longer returned in the order states collection. They remain accessible by ID so existing references in historical orders keep resolving.
Added support for creating and deleting custom URLs for products and categories. Creating a new custom URL automatically slugifies it (CZ/SK ruleset) and deactivates any previously active custom URL on the same urlItem. System URLs cannot be deleted.
System webhooks for package activation and deactivation now include the website locale in the payload (cs_CZ or sk_SK).
Response headers now include rate limit information: X-RateLimit-Request-Cost (cost of the current request), X-RateLimit-Hourly-Remaining (remaining requests in hourly limit), X-RateLimit-Daily-Remaining (remaining requests in daily limit).
Batch request cost has been updated. Previously, all batch requests cost 1. Now the cost equals the number of changed items divided by 10 (rounded up, minimum 1). For example: 1-10 items = cost 1, 11-20 items = cost 2, 21-30 items = cost 3, etc.
Added endpoint for edit trackingNumber and trackingLink properties in orderDeliveryPayment for shipment tracking.
Extended orderDeliveryPayment with trackingNumber and trackingLink properties for shipment tracking.
Added change date for orders.
Added webhook notifications for order changes.