Shoplazza
Shoplazza is a global e-commerce SaaS platform that lets merchants build and run online stores, and lets partners extend the platform through public apps, payment apps, storefront themes, and checkout/theme extensions. Its developer surface is the versioned REST Admin API (date-based vYYYYMM versions served under /openapi/YYYY-MM/), authorized with OAuth 2.0 access tokens and scoped permissions, plus webhooks for store events, an app billing API, App Bridge for embedded admin apps, the Shoplazza CLI, and official OAuth SDKs. Shoplazza is backed by SoftBank Vision Fund. This profile was enriched from Shoplazza's public developer documentation (shoplazza.dev) and its published OpenAPI 3.1 specification.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Shoplazza the way a machine reads it — 27 machine-readable artifacts across 20 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Shoplazza scores 59.9/100 (developing), with a separate agent-readiness read of 78/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Shoplazza
Each block below is one kind of artifact we hold for Shoplazza. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 20
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Shoplazza Access API
The Access API from Shoplazza — 1 operation(s) for access.
Shoplazza App Proxy API
The App Proxy API from Shoplazza — 3 operation(s) for app proxy.
Shoplazza Billing API API
The Billing API API from Shoplazza — 10 operation(s) for billing api.
Shoplazza Custom Area API
The Custom Area API from Shoplazza — 2 operation(s) for custom area.
Shoplazza Customer API
The Customer API from Shoplazza — 6 operation(s) for customer.
Shoplazza Data API
The Data API from Shoplazza — 5 operation(s) for data.
Shoplazza Discounts API
The Discounts API from Shoplazza — 14 operation(s) for discounts.
Shoplazza File API
Upload image materials to the material library and the material library operations of material
Shoplazza Fullfillment API
The Fullfillment API from Shoplazza — 5 operation(s) for fullfillment.
Shoplazza Gift Card API
The Gift Card API from Shoplazza — 3 operation(s) for gift card.
Shoplazza Meta Definition API
The Meta Definition API from Shoplazza — 5 operation(s) for meta definition.
Shoplazza Metafield API
The Metafield API from Shoplazza — 6 operation(s) for metafield.
Shoplazza Order API
The Order API from Shoplazza — 11 operation(s) for order.
Shoplazza Order Risk API
The Order Risk API from Shoplazza — 4 operation(s) for order risk.
Shoplazza Page API
The Page API from Shoplazza — 4 operation(s) for page.
Shoplazza Product API
The Product API from Shoplazza — 21 operation(s) for product.
Shoplazza Redirect API
The Redirect API from Shoplazza — 3 operation(s) for redirect.
Shoplazza Shop API
The Shop API from Shoplazza — 8 operation(s) for shop.
Shoplazza Theme API
The Theme API from Shoplazza — 9 operation(s) for theme.
Shoplazza Webhook API
The Webhook API from Shoplazza — 3 operation(s) for webhook.
Scroll within the panel for all 20 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
shoplazza-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Shoplazza Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Shoplazza Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Shoplazza — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/shoplazza · machine-readable index on apis.io