Skip to content

E-Commerce · Beta

Vilkas
API integration

Ship E-Commerce features without building the integration. Full Vilkas API access via Proxy and 90+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Built for specific customer use cases. Issues are resolved quickly.

Talk to us
Vilkas

Use Cases

Why integrate with Vilkas

Common scenarios for SaaS companies building Vilkas integrations for their customers.

01

Automate Nordic order fulfillment

Shipping and logistics SaaS can poll new Vilkas orders, generate labels with carriers like Posti or Matkahuolto, and push tracking data back to the merchant's shop so end users get a hands-off fulfillment flow.

02

Sync product catalogs from a PIM

PIM and catalog management tools can push products, variations, custom attributes, and category assignments into Vilkas, keeping a merchant's storefront in lockstep with their master catalog without manual data entry.

03

Embed storefront widgets safely

Reviews, chat, personalization, and analytics SaaS can inject their JavaScript into Vilkas shops via script tags, so merchants onboard with one click instead of pasting code into templates.

04

Run loyalty and retention campaigns

Retention platforms can segment Vilkas customers by order history, then auto-create coupon campaigns with single-use codes to reward VIPs or recover abandoned carts.

05

Mirror orders into ERP and accounting

ERP, bookkeeping, and finance SaaS can pull orders, order documents (invoices, credit notes), and customer data from Vilkas to keep financial systems reconciled with live shop activity.

What You Can Build

Ship these features with Truto + Vilkas

Concrete product features your team can ship faster by leveraging Truto’s Vilkas integration instead of building from scratch.

01

Two-way order and tracking sync

List new Vilkas orders, enrich them in your app, and patch shipping data or order status back using the bulk shipping and order update endpoints.

02

One-click storefront script installer

Install and uninstall your widget cleanly on any Vilkas shop by programmatically creating and deleting script tags, no merchant code edits required.

03

Catalog push from a PIM

Create products, variations, slideshow images, cross-sells, and category assignments in Vilkas directly from your product information system.

04

Automated coupon and campaign engine

Spin up coupon campaigns and bulk-generate single-use codes tied to triggers like VIP tiers, re-engagement, or abandoned carts.

05

Customer segmentation and CRM sync

Pull the full customer list with order history to build audiences, score LTV, and sync enriched profiles into marketing or CRM destinations.

06

Invoice and document ingestion

Fetch finalized order documents such as invoices and credit notes to feed accounting, tax, and audit workflows in your SaaS.

SuperAI

Vilkas AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

vilkas_cart_billing_addresses_bulk_update

Modifies the billing address for a cart. Required: cart_id.

vilkas_cart_billing_addresses_bulk_delete

Deletes the billing address from a cart. Required: cart_id.

create_a_vilkas_cart_coupon

Applies a coupon code on a cart which results in creating a couponLineItem and a link to remove the coupon. Required: cart_id, code. Documented for ePages 6 shops only; may not be available on Vilkas Now.

delete_a_vilkas_cart_coupon_by_id

Deletes a coupon line item from a specific cart and recalculates cart. The link to add a coupon appears in the links section. Required: id, cart_id. Documented for ePages 6 shops only; may not be available on Vilkas Now.

vilkas_cart_line_item_prices_bulk_update

Modifies the price of a specific product line item in a cart. Required: cart_id, line_item_id.

create_a_vilkas_cart_line_item

Creates a product line item in a cart. Required: cart_id.

update_a_vilkas_cart_line_item_by_id

Modifies a specific product line item in a cart. Required: id, cart_id.

delete_a_vilkas_cart_line_item_by_id

Deletes a specific product line item from a cart. Required: id, cart_id.

vilkas_cart_line_items_bulk_create

Creates multiple product line items in a cart. Required: cart_id.

create_a_vilkas_cart_order

Creates an order that is valid at the time of cart creation. It won't be validated again while processing the actual request. Billing address has to be available in the cart before creating an order. The request body for this REST call remains empty. Required: cart_id.

vilkas_cart_payment_data_bulk_update

Modifies the payment data for a cart.

Please note that by providing the attribute name in the request body, the attributes paymentMethod and transactionId included in paymentData will be set to null. The provided name will not be included in the response. Required: cart_id.

vilkas_cart_shipping_addresses_bulk_update

Modifies the shipping address for a cart. Required: cart_id.

vilkas_cart_shipping_addresses_bulk_delete

Deletes the shipping address from a cart. Required: cart_id.

vilkas_cart_shipping_data_bulk_update

Modifies the shipping data for a cart. Required: cart_id.

list_all_vilkas_carts

Returns a list of carts. The connector pages through all results (up to 100 per page).

create_a_vilkas_cart

Creates a cart for a shop.

get_single_vilkas_cart_by_id

Returns a specific cart from a shop identified by the provided cart Id. Required: id.

list_all_vilkas_categories

Returns the product categories of the shop. This usually is the default root category "Categories", but can also include additional root categories, if supported by the shop.

get_single_vilkas_category_by_id

Returns the category identified by the provided category ID. Required: id.

update_a_vilkas_category_by_id

Modifies a category identified by the provided category ID. Required: id.

delete_a_vilkas_category_by_id

Deletes a category identified by the provided category ID. Required: id. Documented for ePages 6 shops only; may not be available on Vilkas Now.

list_all_vilkas_category_sequences

Returns the order of subcategories for the provided category ID as an array. If the category has no subcategories, an empty array will be returned. Required: category_id.

vilkas_category_sequences_bulk_update

Updates the order of subcategories for the provided category ID. Note that it is only possible to change the order but not to delete a subcategory. Required: category_id.

create_a_vilkas_category_subcategory

Creates a subcategory to an existing category. Providing attributes in the request is optional. Required: category_id.

list_all_vilkas_countries

Returns all supported countries of the shop, i.e. all countries that can be selected as delivery countries for orders placed in the shop.

vilkas_coupon_campaign_coupons_bulk_update

Creates a coupon code in a coupon campaign. Required: coupon_campaign_id, code.

create_a_vilkas_coupon_campaign

Creates a coupon campaign for a shop. Coupon campaign types can be FIX (absolute value), PERCENT (percentage value), and SHIPPING (waive delivery costs). Required: locale.

get_single_vilkas_coupon_campaign_by_id

Returns a specific coupon campaign from a shop identified by the provided coupon campaign Id. Required: id.

list_all_vilkas_currencies

Returns the currency information of a shop.

list_all_vilkas_customers

Returns a list of all customers. The connector pages through all results (up to 100 per page).

create_a_vilkas_customer

Creates a customer. If *customerNumber* is not provided in the request, it will be generated automatically.

get_single_vilkas_customer_by_id

Returns a specified customer of a shop. Required: id.

update_a_vilkas_customer_by_id

Updates information for a single customer with partial data according to RFC 6902. You can either add or remove certain attributes.

*Supported JSON-PATCH operations*
- add (sets or replaces an attribute)
- remove (unsets an attribute)

*Attribute paths that allow updates via PATCH* ( ¹ supports *add* only)
- /customerNumber¹
- /billingAddress
- /internalNote
. Required: id. Send a JSON Patch array (RFC 6902) as the body.

list_all_vilkas_legal

Returns hyperlinks of legal information for a shop.

list_all_vilkas_legal_contact_information

Returns the contact information of a shop.

vilkas_legal_contact_information_bulk_update

Modifies the contact information of a shop. This endpoint expects a complete object representation, all fields included. If any field is not set, it will be deleted from the transferred object. Required: locale.

list_all_vilkas_legal_cookie_policy

Returns the cookie policy of a shop.

vilkas_legal_cookie_policy_bulk_update

Modifies the cookie policy of a shop. This endpoint expects a complete object representation, all fields included. If any field is not set, it will be deleted from the transferred object. Required: locale.

list_all_vilkas_legal_privacy_policy

Returns the privacy policy of a shop.

vilkas_legal_privacy_policy_bulk_update

Modifies the privacy policy of a shop. This endpoint expects a complete object representation, all fields included. If any field is not set, it will be deleted from the transferred object. Required: locale.

list_all_vilkas_legal_rights_of_withdrawal

Returns the customer rights of withdrawal of a shop.

vilkas_legal_rights_of_withdrawal_bulk_update

Modifies the customer rights of withdrawal of a shop. This endpoint expects a complete object representation, all fields included. If any field is not set, it will be deleted from the transferred object. Required: locale.

list_all_vilkas_legal_shipping_information

Returns detailed information on possible shipping types and the costs incurred. Also displays the costs for shipment abroad.

vilkas_legal_shipping_information_bulk_update

Modifies the shipping information of a shop. This endpoint expects a complete object representation, all fields included. If any field is not set, it will be deleted from the transferred object. Required: locale.

list_all_vilkas_legal_terms_and_conditions

Returns the terms and conditions of a shop.

vilkas_legal_terms_and_conditions_bulk_update

Modifies the terms and conditions of a shop. This endpoint expects a complete object representation, all fields included. If any field is not set, it will be deleted from the transferred object. Required: locale.

list_all_vilkas_locales

Returns the shop's locale information, i.e. the language identifier and the region identifier.

list_all_vilkas_newsletter_campaign_subscribers

Returns all subscribers of a newsletter campaign from a shop. Required: campaign_id. Documented for ePages 6 shops only; may not be available on Vilkas Now. The connector pages through all results (up to 100 per page).

list_all_vilkas_newsletter_campaigns

Returns all newsletter campaigns of a shop. Documented for ePages 6 shops only; may not be available on Vilkas Now. The connector pages through all results (up to 100 per page).

list_all_vilkas_order_documents

Returns finalized invoice and credit note order documents by orderId. Required: order_id. The connector pages through all results (up to 100 per page).

list_all_vilkas_orders

Returns a list of orders. By default the results for orders are sorted by creationDate. The connector pages through all results (up to 100 per page).

get_single_vilkas_order_by_id

Returns information for a single order identified by the provided order ID. Required: id.

update_a_vilkas_order_by_id

Updates information for a single order with partial data according to RFC 6902. You can either add or remove certain attributes. Note that an order cannot be updated once it is in edit mode. In that case, response code 409 will appear. Required: id. Send a JSON Patch array (RFC 6902) as the body.

create_a_vilkas_product_availability_notification

Enables the availability notification for the given product and customer email address. The language of the notification is based on the locale of the customer's storefront. Required: product_id.

create_a_vilkas_product_category_assignment

Assigns categories to products and products to categories. Required: categoryId, productId.

vilkas_product_category_assignments_bulk_delete

Deletes one or more products from a category. Required: categoryId, productId. Documented for ePages 6 shops only; may not be available on Vilkas Now.

list_all_vilkas_product_cross_selling

Returns information on the cross-selling assignments of a single product. Required: product_id.

vilkas_product_cross_selling_bulk_update

Modifies information on the cross-selling assignments of a single product by replacing all of the assignments. Required: product_id.

vilkas_product_cross_selling_bulk_patch

Updates information on the cross-selling assignments for a single product with partial data according to RFC 6902. You can either add or remove assignments. Required: product_id.

list_all_vilkas_product_custom_attributes

Returns values of user-defined product attributes. Required: product_id.

vilkas_product_custom_attributes_bulk_update

Updates information on the custom attributes for a single product with partial data according to RFC 6902. You can either add or remove assignments.

*Supported JSON-PATCH operations*
- add (sets or replaces an attribute value)
- remove (unsets an attribute)

. Required: product_id.

list_all_vilkas_product_exports

Returns a CSV file with all products of the shop. Note that after the first installation of the app by a merchant, the export file will not be available until the next day.

list_all_vilkas_product_lowest_prices

Returns the lowest price of all variations of a product that can currently be purchased.
Returns 404 Not Found if the product does not have any variation with an independent price, e.g. if all variations share the same price. Also depends on the shop setting to display "from" prices. Required: product_id. Documented for ePages 6 shops only; may not be available on Vilkas Now.

list_all_vilkas_product_slideshow_images

Returns links to the slideshow images of a product. Slideshow images are all images uploaded for a product. Required: product_id.

create_a_vilkas_product_slideshow_image

Creates (uploads) an image for the product slideshow. The product slideshow reflects all images uploaded for the product. To determine the slideshow image that should serve as the main image for the product, refer to the respective PATCH endpoint. Required: product_id, filename, name, image.

delete_a_vilkas_product_slideshow_image_by_id

Deletes a single image from the product slideshow. The product slideshow reflects all images uploaded for the product. Required: id, product_id.

list_all_vilkas_product_slideshow_sequences

Returns the names of the slideshow images as an array. Slideshow images are all images uploaded for the product. They are displayed in the same order as they are included in the array. Required: product_id.

vilkas_product_slideshow_sequences_bulk_update

Updates the sequence of the slideshow images. Slideshow images are all images uploaded for the product. They will be displayed in the same order as they are provided in the array. Required: product_id.

list_all_vilkas_product_suggestions

Returns suggestions for a product search query. Required: query. Documented for ePages 6 shops only; may not be available on Vilkas Now.

list_all_vilkas_product_types

Returns a list of all product types. The connector pages through all results (up to 100 per page).

create_a_vilkas_product_type

Creates a product type.

get_single_vilkas_product_type_by_id

Returns a specified product type of a shop. Required: id.

update_a_vilkas_product_type_by_id

Updates information for a single product type with partial data according to RFC 6902. You can either add or remove certain attributes. Required: id. Send a JSON Patch array (RFC 6902) as the body.

list_all_vilkas_product_variations

Returns a list of product variations.
The response contains links to the listed product variations and the attributes name and value that were used for creating those variations. Note that the default amount of results per page is 100. The maximum amount of results displayed per page is 1000 for this resource. Required: product_id. Documented for ePages 6 shops only; may not be available on Vilkas Now. The connector pages through all results (up to 1000 per page).

create_a_vilkas_product_variation

Creates new product variations. Required: product_id.

list_all_vilkas_products

Returns a list of products. The connector pages through all results (up to 100 per page).

create_a_vilkas_product

Creates a new product.

get_single_vilkas_product_by_id

Returns information on a single product. For product variations, a link to the respective product variations resource (rel="variations") is added. Note that the attribute minStocklevel is only available with the products_write authorisation. Required: id.

update_a_vilkas_product_by_id

Updates information for a single product with partial data according to RFC 6902. You can either add or remove certain attributes. Required: id. Send a JSON Patch array (RFC 6902) as the body.

delete_a_vilkas_product_by_id

Deletes a single product. Required: id.

vilkas_products_lookup

Returns a list of products that match a specified SKU.

vilkas_products_search

Performs a product search using facets.

list_all_vilkas_sales

Returns the summary of sales figures for a specified product or for the shop grouped by currencies. The amounts are gross and net amounts. By default the results of the last 30 days are displayed. Open-ended queries are limited to 30 days. The maximum time frame for displaying orders is 1 year.

list_all_vilkas_script_tags

Returns a list of all script tags for a shop.

create_a_vilkas_script_tag

Creates a new script tag.

delete_a_vilkas_script_tag_by_id

Deletes a script tag identified by the provided script tag ID. Using this call, only deletes the script tags created by an application, not all the script tags of a shop. Required: id.

list_all_vilkas_shipping_methods

Returns the shipping methods of a shop.

get_single_vilkas_shipping_method_by_id

Returns a specific shipping method of a shop identified by the provided shipping method Id. Required: id.

list_all_vilkas_shop_info

Returns the public information of a shop, like name, slogan and logo.

list_all_vilkas_tax_classes

Returns all tax classes of a shop. The connector pages through all results (up to 100 per page).

get_single_vilkas_tax_class_by_id

Returns a specific tax class of a shop identified by the provided tax class Id. Required: id.

list_all_vilkas_tax_model

Returns the tax model of the shop.

list_all_vilkas_updated_products

Returns all updated products together with the time of their last update. Required: product_property.

list_all_vilkas_watched_products

Returns a list of all watched products. Watched products refers to items currently out of stock and therefore can be watched by online shop customers. The connector pages through all results (up to 100 per page).

Why Truto

Why use Truto’s MCP server for Vilkas

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1050+ integrations.

01

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

02

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

03

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

04

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

05

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

06

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Start with Vilkas in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.

01

Link your customer’s Vilkas account

Use Truto’s frontend SDK to connect your customer’s Vilkas account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

02

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

03

Call our API, we call Vilkas

Truto’s Proxy API is a 1-to-1 mapping of the Vilkas API. You call us, we call Vilkas, and pass the response back in the same cycle.

04

Unified response format

Every response follows a single format across all integrations. We translate Vilkas’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Vilkas on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

How does authentication to Vilkas work through Truto?

Vilkas is built on the ePages REST API and uses token-based authentication scoped to a merchant's shop. Truto handles the credential exchange and storage so your end users connect their Vilkas shop once and your app calls the tools without managing tokens directly.

Which Vilkas resources can I read and write today?

The available tools cover carts, orders, order documents, customers, products (including variations, custom attributes, cross-selling, and slideshow images), categories and category sequences, coupons and coupon campaigns, script tags, shipping methods, tax classes, legal pages, newsletters, and shop metadata.

How do I keep order and product data fresh?

You can poll endpoints like list_all_vilkas_orders, list_all_vilkas_updated_products, and list_all_vilkas_customers on a schedule. Truto normalizes pagination so you can incrementally sync without re-implementing per-endpoint cursors.

Can I update orders partially instead of replacing the whole record?

Yes. Order updates use JSON-PATCH semantics via update_a_vilkas_order_by_id, which is ideal for patching fulfillment status, tracking numbers, or shipping data without overwriting other fields.

How do I install my app's frontend code on a merchant's Vilkas storefront?

Use create_a_vilkas_script_tag to inject your JavaScript into the storefront, and delete_a_vilkas_script_tag_by_id to remove it on uninstall. This is the supported way to embed widgets without editing shop templates.

Does Truto support bulk operations for Vilkas?

Yes. Several Vilkas tools are bulk-native, including cart line items, shipping and billing addresses, product custom attributes, cross-selling, category sequences, coupon campaign coupons, and legal content updates, so you can push large changesets efficiently.

Are custom product attributes supported?

Yes. You can list and bulk-update product custom attributes, which is useful for B2B specs, SKUs with extended metadata, or industry-specific fields that go beyond the default product schema.

Vilkas

Get Vilkas integrated into your app

Our team understands what it takes to make a Vilkas integration successful. A short, crisp 30 minute call with folks who understand the problem.