API glossary
Last updated
Was this helpful?
Build appsContact API support
Build apps
Last updated
Was this helpful?
A one-for-all tool, where users can manage all aspects of their store: products, orders, customers, website, integrations, etc.
Extension users can install to their Ecwid stores that adds some new functionality, integration, or a way to customize store content or design.
Anyone who creates an Ecwid store is considered a user: site owners, merchants, and developers helping other users with managing their sites and business.
Website builder created by Ecwid that allows creating for both ecommerce and non-ecommerce sites.
Native UI for building Ecwid websites available to all Ecwid users right from the Ecwid admin.
Marketplace with applications that extend store functionality, add new ways of customization, or integrate a store with another service, for example, payment provider, CRM system, shipping rates calculator, etc.
Private application for accessing Ecwid API in a specific store. Ecwid creates one custom app for any user who visits the app dashboard in Ecwid admin for the first time.
Hidden page in Ecwid admin where developers can create new applications, check app settings, get access tokens, and request application updates.
Permission for the app to do a specific action or access some data in the store. For example, the read_orders scope allows the app to get information about orders placed in the store and the add_payment_method scope allows the app to add a new online payment method to the checkout.
Unchangeable and unique credentials for app authentication and decoding some API requests.
Every application has two API keys: client_id (app ID) and client_secret (app secret).
An app key used to identify the particular application. For public apps, the app ID often matches with the app name. In API, we refer to this ID as the app’s client_id.
Unique authentication key of an app that must be kept hidden and secure as it grants access to app authentication. In documentation, reffered as client_secret.
Secure app credentials for authorizing REST API requests. If an app is installed in several Ecwid stores, it has unique access tokens for every store.
There are two tokens: secret_token and public_token. Learn more about app access tokens: App settings
Link to a self-hosted server URL connected to the app that enables a specific feature. For example, the paymentUrl endpoint allows you to receive online payment requests from your store through the app.
An app available in the . Learn more about publishing your app: Launch apps
Go to the