Ecwid API

Name: Ecwid API API
Brand: Ecwid API
Availability: InStock

✓ Official Vendor SpecE CommerceStorefrontbearer27 EndpointsREST

For Agents

Manage Ecwid store products, orders, customers, categories, and discounts with bearer-token authentication scoped to a storeId.

Quickstart

Get started with Ecwid API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list ecwid orders and update product"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Ecwid API API.

Search, create, update, and delete products in an Ecwid store catalogue

Manage orders end to end including search, retrieve, update, and delete by orderNumber

Read and update the store profile to keep merchant settings in sync

Manage customers and customer groups for personalised pricing and outreach

GET STARTED

Start building with Ecwid API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Ecwid API API for, with concrete tasks.

★ Product Catalogue Sync

Merchants running Ecwid alongside an ERP or PIM need product records to flow in both directions. The Ecwid API exposes GET /products, POST /products, PUT /products/{productId}, and DELETE /products/{productId} so an integration can keep titles, prices, and stock numbers aligned. Each product call is scoped to the storeId in the base URL so multi-store merchants can run parallel syncs.

Pull the ERP product list, GET /products from Ecwid, and POST or PUT updates so titles, prices, and stock match.

Order Fulfilment Pipeline

Fulfilment systems poll Ecwid for new orders, update status as packages move through the warehouse, and write tracking numbers back to the order record. The orders endpoints — GET /orders, GET /orders/{orderNumber}, PUT /orders/{orderNumber}, and DELETE /orders/{orderNumber} — cover the lifecycle. The merchant sees fulfilment progress directly in the Ecwid admin without manual updates.

GET /orders filtered by 'awaitingProcessing', PUT /orders/{orderNumber} with the new fulfilment status and tracking, and confirm the response.

Customer Relationship Workflow

Ecwid stores hold customer records that downstream marketing and CRM systems want. The API surfaces customer records and groupings so an integration can segment by group, retrieve order history, and build targeted email or SMS flows in another tool. Customers stay scoped to the storeId, keeping multi-store deployments cleanly separated.

List Ecwid customers by group, push qualifying customers into the marketing CRM, and tag them with their Ecwid customer group.

Storefront Profile and Discounts Management

Operations teams update Ecwid store settings and discounts through the API rather than the admin UI when they manage many stores. GET /profile and PUT /profile expose the store configuration, while the discounts resource manages coupon-style rules that apply at checkout. This is useful for chains of branded storefronts that share configuration patterns.

GET /profile for each storeId in scope, compare against the canonical settings, and PUT /profile to bring outliers back in line.

AI Agent Storefront Operations

An AI agent embedded in a merchant's operations stack can use Jentic to discover Ecwid product, order, and customer endpoints and run a multi-step workflow — adjust pricing, fulfil orders, and update customer notes — based on natural-language requests. Jentic delivers the bearer token and operation schemas into the agent's context for each step.

Through Jentic, search 'list ecwid orders' and 'update ecwid product price', load the schemas, and execute the chosen flow against the merchant's storeId.

Key Endpoints

27 endpoints — ecwid is a storefront platform that lets businesses sell across their own website, social channels, and marketplaces.

METHOD

PATH

DESCRIPTION

GET

/products

Search products

POST

/products

Create a product

PUT

/products/{productId}

Update a product

GET

/orders

Search orders

GET

/orders/{orderNumber}

Retrieve an order

PUT

/orders/{orderNumber}

Update an order

GET

/profile

Get store profile

GET

/products

Search products

POST

/products

Create a product

PUT

/products/{productId}

Update a product

GET

/orders

Search orders

GET

/orders/{orderNumber}

Retrieve an order

PUT

/orders/{orderNumber}

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Ecwid bearer token, scoped to a specific storeId, is stored encrypted in the Jentic vault. Agents receive the operation and Jentic injects the Authorization header at call time so the raw token never enters the agent's context.

Intent-based discovery

Agents search natural-language intents like 'list ecwid orders' or 'update ecwid product price' and Jentic returns the matching /orders or /products operations with their input schemas, so the agent can call the right endpoint without reading the Ecwid developer portal.

Time to first call

Direct Ecwid integration takes 1-2 days to handle bearer tokens, storeId routing, pagination, and webhook reconciliation. Through Jentic the search-load-execute flow is under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify Admin API

Larger e-commerce platform with deeper merchant tooling and apps

Choose Shopify when the merchant has outgrown Ecwid's storefront and wants the broader Shopify ecosystem.

Complementary

eBay Fulfillment API

Marketplace order management for merchants who also list on eBay

Use eBay Fulfillment alongside Ecwid when the merchant fulfils orders from both their Ecwid store and eBay.

Complementary

ECOMMPAY API

Payments orchestration that can sit beneath an Ecwid storefront

Use ECOMMPAY for payment orchestration in markets where Ecwid's built-in payment integrations don't cover the merchant's needs.

FAQs

Specific to using Ecwid API API through Jentic.

What authentication does the Ecwid API use?

The Ecwid API uses HTTP bearer-token authentication (the bearerAuth scheme) with a token scoped to a specific storeId in the base URL. Through Jentic, the bearer token is stored encrypted in the Jentic vault and injected into the Authorization header at call time.

Can I create products in an Ecwid store via the API?

Yes. POST /products accepts the product payload (title, price, stock, images) and the response returns the new productId. PUT /products/{productId} handles subsequent updates.

What are the rate limits for the Ecwid API?

The OpenAPI spec does not declare rate limits. Ecwid applies platform-level throttling per storeId; for high-volume sync jobs, batch reads via GET /products with pagination rather than fetching products individually.

How do I update an Ecwid order's status through Jentic?

Search 'update ecwid order' in Jentic, load the PUT /orders/{orderNumber} schema, pass the new fulfilment status and tracking number, and Jentic submits the call against the merchant's storeId.

Does the Ecwid API support multi-store merchants?

Yes. The base URL https://app.ecwid.com/api/v3/{storeId} embeds the storeId, and the bearer token is scoped to that store. To work across multiple stores, an agent uses one credential per storeId.