Help CenterHelp Center / Developers · Concept
Which plans include webhooks, the APIs and ERPNext, and what each one does when your plan does not include it.
Two plan features cover everything in this section.
| Plan feature | What it unlocks | Plans that include it |
|---|---|---|
| Webhooks & developer API | Shop Webhooks, the incoming API, the Shop API | Growth, Scale, Enterprise |
| ERP & accounting (ERPNext, Zoho) | The ERPNext switch on the Integrations tab | Growth, Scale, Enterprise |
Starter does not include either. The pricing card shows them as "API & webhooks" and "Zoho & ERPNext sync". See Plans and limits.
| Part | Behaviour |
|---|---|
| Shop › Shop Webhooks | The menu item is hidden. Opening the address sends you to the dashboard with the message below |
| Webhooks you already created | They stay saved. Nothing is sent. Sending starts again when the plan includes the feature |
Incoming API (/api/webhook/...) | Every call answers HTTP 402 |
| Shop API bulk update | Answers HTTP 402 |
| Item webhook and User webhook switches | Read as off and are locked with a Managed by platform badge |
| Enabled under ERPNext Configurations | Reads as off and is locked the same way. No orders are sent |
The 402 answer is JSON:
{
"success": false,
"message": "Webhooks & developer API is not included in your plan. Upgrade your plan (Plan & billing) to use it.",
"upgrade": true,
"feature": "qc_api_webhooks"
}
Shop › Whatsapp Api & Webhooks is not behind the plan feature. You can create an API token on any plan. The Shop API call that uses it is still checked.
A shop whose plan has ended is read-only until it is renewed.
All three screens are in the shop owner's Shop menu. Staff menus do not show them. A developer does not need a panel login: the owner copies the token and sends it over a private channel.