-
Integrations
- Articles coming soon
-
Marketing
-
- Advertising white-label eCommerce solution to your customer ecosystem
- Advertising compliance and brand usage guidelines for partners
- How to create high-converting advertisements for your eCommerce platform
- How to run advertising campaigns to attract online merchants and resellers
- How to measure advertising performance and generate qualified merchant leads
-
- How to promote your eCommerce platform using consistent branding
- White-Label eCommerce branding strategy for partners
- Crafting effective brand messaging for eCommerce platforms
- Positioning your eCommerce platform for different merchant segments
- Maintaining brand consistency across marketing channels
-
- Creating High-Impact eCommerce marketing assets for partners
- Designing eCommerce sales decks that convert merchants
- Creating eCommerce landing pages that convert traffic into merchants
- Creating eCommerce case studies that build trust and close deals
- Creating Email campaigns that drive eCommerce adoption
-
-
Partner Hub
-
- Articles coming soon
-
- Articles coming soon
-
-
Sales
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
Technical and Support
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
-
-
- Payment methods at eCommerce Store
- Setting up Stripe Payment Gateway
- Setting up Paypal in your Online Store
- Setting up CashFree Gateway
- Setting up RazorPay Gateway
- Setting up Paystack gateway
- Setting up Flutterwave Gateway
- Setting up Mercado Pago Gateway
- Setting up Mamo Pay Gateway
- Setting up Yoco Gateway
- Setting up Nets Easy Gateway
- Setting up Vipps Gateway
- Setting up Mollie Gateway
- Setting up Epoint Gateway
- Setting up Iyzico Gateway
- Setting up Payriff Gateway
- Setting up Crypto Payments through Nicky
- What is Cash on Delivery?
- Show Remaining Articles (3) Collapse Articles
-
- How to create an analytics account?
- Connecting Google Analytics to your eCommerce store
- Connecting Meta Pixel to your eCommerce store
- Connecting Tik Tok Pixel to your eCommerce store
- Connecting Google Tag Manager to your eCommerce store
- Managing product reviews & ratings in your eCommerce store
- Using marketing automation to drive urgency and social proof
- Setting up your LLMs.txt integration to boost your AI search visibility
- Automating manual order fulfilment and live tracking with Shiprocket
- Automating search engine discoverability with dynamic sitemaps
- Automate, optimise, scale: Building your Google shopping product feed
- How to sync your product catalog with meta ads to drive more sales
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
Print
Posted
Updated
Byadmin
HTTP API for merchants and integration partners to manage a Zencommerce store the same way as the accounts and admin web apps: sign in → select a store → run catalog, orders, customers, content, and settings operations.
Audience: external developers and technical partners
API prefix: /v1/account/api
Getting started
Base URL
API_BASE="https://core-api.myzencommerce.in"
Auth flow (same as the web apps)
- Account login → account access_token + refresh_token
- List shops or create a shop (account Bearer)
- Shop access-token for a shop id → shop access_token + refresh_token
- Call all store operations with the shop Bearer token
Authorization: Bearer {token}
| Token | Used for |
| Account access_token | /auth/me, /auth/logout, /shops (list/create/check-availability), /shops/{id}/access-token |
| Shop access_token | Products, orders, customers, settings, … (everything under shop scope) |
Account tokens expire in 6 hours; account refresh tokens in 24 hours.
Shop tokens expire in 6 hours; shop refresh tokens in 24 hours.
Request formats
| Format | Usage |
| application/json | Most operations |
| multipart/form-data | Uploads (/uploads, product/collection images) |
Quick start
1) Login (no Bearer required)
curl -sS -X POST "$API_BASE/v1/account/api/auth/login" \
-H "Content-Type: application/json" \
-d '{"email":"you@example.com","password":"YOUR_PASSWORD"}'
Note: Save access_token and refresh_token from the response
ACCOUNT_TOKEN="..."
ACCOUNT_REFRESH="..."
2) List shops (or create one with POST /v1/account/api/shops)
curl -sS "$API_BASE/v1/account/api/shops" \
-H "Authorization: Bearer $ACCOUNT_TOKEN"
3) Select a shop (replace SHOP_ID)
curl -sS -X POST "$API_BASE/v1/account/api/shops/SHOP_ID/access-token" \
-H "Authorization: Bearer $ACCOUNT_TOKEN"
SHOP_TOKEN="..." # shop access_token
SHOP_REFRESH="..." # shop refresh_token
4) Call shop-scoped APIs
curl -sS "$API_BASE/v1/account/api/products" \
-H "Authorization: Bearer $SHOP_TOKEN"
Errors
Error bodies commonly look like:
{
"message": "Human-readable message",
"code": 400,
"errors": null
}
| HTTP | Typical meaning |
| 401 | Missing/invalid/expired token |
| 403 | Forbidden (e.g. missing refresh token) |
| 404 | Resource not found or wrong credentials on login |
| 400 | Validation / business rule failure |