How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Virto Commerce

Virto Commerce Store API

Multi store management with individual store settings

Documentation Provider Profile APIs.io OpenAPI GitHub

Virto Commerce Store API is one of 13 APIs that Virto Commerce publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Store. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 13 operations across 9 paths, and defines 19 schemas. It is described by OpenAPI 3.0.4, at version v1.

Requests are made against the base URL https://virtostart-demo-admin.govirto.com/api.

13 operations 9 paths 19 schemas 1 DELETE6 GET1 PATCH3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.4
API Version
v1
Base URL
https://virtostart-demo-admin.govirto.com/api
Authentication
OAuth 2.0, API Key, API Key, HTTP Signature, HTTP Basic
Resource Areas
1

Authentication & Security 5

Virto Commerce Store API declares 5 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the password and clientCredentials flows. An API key is passed in the query as api_key (api_key). An API key is passed in the header as api_key (api_key_header). It uses HTTP signature authentication (http-signature). It accepts HTTP basic authentication (basic).

  • oauth2 — OAuth2 Resource Owner Password Grant flow
  • api_key — API Key authentication
  • api_key_header — API Key authentication (alternative via header)
  • http-signature — HTTP Signature authentication using Authorization header
  • basic — Basic authentication using username and password

Paths & Operations 13

Across 9 paths, the API surfaces 13 operations — 1 DELETE, 6 GET, 1 PATCH, 3 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Store 13

Multi store management with individual store settings

GET
/api/store-authentication-schemes/{storeId}
StoreAuthenticationScheme_Get 1 param → 200401403
PUT
/api/store-authentication-schemes/{storeId}
StoreAuthenticationScheme_Update 1 param body → 204401403
POST
/api/stores/search
Search stores
StoreModule_SearchStores body → 200401403
GET
/api/stores/{id}
Get store by id
StoreModule_GetStoreById 2 params → 200401403
PATCH
/api/stores/{id}
Partial update for the specified store by id
StoreModule_PatchStore 1 param body → 204401403
GET
/api/stores/outer/{outerId}
Gets store by outer id.
StoreModule_GetStoreByOuterId 2 params → 200401403
POST
/api/stores
Create store
StoreModule_CreateStore body → 200401403
PUT
/api/stores
Update store
StoreModule_UpdateStore body → 204401403
DELETE
/api/stores
Delete stores
StoreModule_DeleteStore 1 param → 204401403
POST
/api/stores/send/dynamicnotification
Send dynamic notification (contains custom list of properties) to store or administrator email
StoreModule_SendDynamicNotificationToStoreEmail body → 204401403
GET
/api/stores/{storeId}/accounts/{id}/loginonbehalf
Check if given contact has login on behalf permission
StoreModule_GetLoginOnBehalfInfo 2 params → 200401403
GET
/api/stores/allowed/{userId}
Returns list of stores which user can sign in
StoreModule_GetUserAllowedStores 1 param → 200401403
GET
/api/stores/{id}/public-settings
StoreModule_GetStorePublicSettingsById 1 param → 200

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are Store (37 properties), ObjectSettingEntry (20 properties), SeoInfo (18 properties), DynamicObjectProperty (17 properties). Each schema is shown below with its type and property counts.

StoreState
string
SeoInfo
object
18 properties
DynamicPropertyValueType
string
Store
object
37 properties
DynamicPropertyObjectValue
object
8 properties
DynamicObjectProperty
object
17 properties
LoginOnBehalfInfo
object
Represent result for checking of possibility login on behalf request
2 properties
StoreAuthenticationScheme
object
10 properties
SortInfo
object
2 properties
StoreSearchCriteria
object
14 properties
Operation
object
4 properties
StoreSearchResult
object
2 properties
SettingValueType
string
ModulePublicStoreSettings
object
2 properties
DynamicPropertyName
object
2 properties
SortDirection
string
ObjectSettingEntry
object
20 properties
PublicStoreSetting
object
2 properties
SendDynamicNotificationRequest
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

virto-commerce-store-api-openapi.yml Raw ↑

Other APIs Virto Commerce publishes across the network.

Virto Commerce Catalog API
AE Profile APIs.io
Virto Commerce Companies and Contacts API
AE Profile APIs.io
Virto Commerce Inventory API
AE Profile APIs.io
Virto Commerce Marketing API
AE Profile APIs.io
Virto Commerce Order Management API
AE Profile APIs.io
Virto Commerce Pricing API
AE Profile APIs.io
Virto Commerce Quotes API
AE Profile APIs.io
Virto Commerce Shopping Cart API
AE Profile APIs.io
Virto Commerce VirtoCommerce Platform API
AE Profile APIs.io
Virto Commerce Webhooks API
AE Profile APIs.io
Virto Commerce Event Bus API
AE Profile APIs.io
Virto Commerce Returns API
AE Profile APIs.io
#Store
← Back to V APIs
API Details
ID
virto-commerce:virto-commerce-store-api
Base URL
https://virtostart-demo-admin.govirto.com/api
Docs
https://docs.virtocommerce.org/
Provider
Virto Commerce
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=virto-commerce-store-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/virto-commerce-store-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Virto Commerce Store API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.