We have launched a new developer page for the wwidgets API. It explains the REST API with ready-to-use examples in cURL, JavaScript, PHP and Python, includes a Q&A helper for quick answers, and documents the sales webhook that turns real orders into notifications without an API key. If you build or run online stores and want to automate your widgets, the wwidgets developer page is the place to start.
What is new?
wwidgets has offered a REST API for campaigns, widgets and statistics for some time. What was missing was one clear place that explains how to use it, with examples you can copy into your own project. The new developer page brings everything together:
- REST API overview: how authentication works, what you can read and change, and how responses are structured.
- Examples in four languages: cURL for quick tests in the terminal, JavaScript for front-end and Node.js projects, PHP for WordPress, WooCommerce and Magento developers, and Python for scripts, data work and automation.
- A Q&A helper: a quick way to find answers to common questions without reading the whole page.
- The sales webhook: how to send real orders to a Recent sales widget so that the notifications on your site reflect genuine purchases.
Who is the developer page for?
It is written for anyone who wants wwidgets to work with other systems rather than only through the dashboard:
- Developers and agencies managing widgets for several client sites.
- Store owners with some technical knowledge who like to automate repetitive tasks.
- Teams who want widget statistics in their own reports and dashboards.
- Shop owners who want real order data in their social proof notifications.
If you only use the dashboard, nothing changes for you. Everything still works as before. The API is an extra option for people who want it.
What can you build with the wwidgets API?
Here are some practical ideas we had in mind while writing the page. None of them require a large project; most are a short script or a small integration.
Sync campaigns with your own systems
If you plan promotions in another tool, you can create or update campaigns in wwidgets from there instead of doing the same work twice. An agency could, for example, keep a list of seasonal campaigns for each client and push them to wwidgets when the season starts.
Switch widgets on and off on a schedule
A countdown timer for a weekend sale should appear on Friday and disappear on Monday. A WhatsApp button might only make sense during your opening hours. With a small scheduled job (a cron job, a serverless function or a task in your automation tool), you can toggle widgets at exactly the right time without logging in.
Pull weekly statistics into your dashboards
The API gives you access to the same statistics you see in wwidgets: impressions, hovers, clicks, form submissions, CTR and conversion rate. A short Python or PHP script can fetch them every week and add them to a spreadsheet, a reporting tool or a client report. That makes it easier to compare widget performance with your sales data in one place.
Send WooCommerce or Shopify orders to your sales widget
This is the use case many store owners ask about. Instead of showing generic notifications, you can send each real order to a Recent sales widget. The notification then shows a genuine purchase, which keeps your social proof honest.
How does the sales webhook work?
The sales webhook is the simplest integration we offer, and it does not need an API key. Your Recent sales widget gives you a webhook address. You send order details to it when a purchase is completed, and the widget shows the order as a notification on your site.
For WooCommerce, the natural place to do this is the payment complete hook, which fires when an order has been paid. A few lines of PHP in your theme or a small plugin are enough. For Shopify and other platforms, you can send the order from your own webhook handler or an automation tool. The developer page shows example payloads and code in each of the four languages.
Because the webhook does not use your API key, you can hand the webhook address to a developer who only needs to connect orders, without sharing access to the rest of your account.
Request limits and access
A few practical details you should know before you start:
| Topic | Details |
|---|---|
| API type | REST API for campaigns, widgets and statistics |
| Examples | cURL, JavaScript, PHP and Python |
| Request limit | 60 requests per minute |
| Plan | Included in E-Commerce World (€14/month) and in the 14-day free trial |
| API key | Account, then API, in your wwidgets dashboard |
| Sales webhook | No API key needed |
The limit of 60 requests per minute is plenty for scheduled jobs, statistics exports and campaign syncing. If you are building something that runs often, add a short pause between requests and cache results where you can, rather than calling the API on every page view.
How to get started
- Start a trial or use your E-Commerce World account. The API is included in the E-Commerce World plan and is available during the 14-day free trial, so you can test it before you decide.
- Get your API key. In the dashboard, go to Account, then API, and copy your key. Keep it private and do not put it in front-end code that visitors can see.
- Open the developer page. Pick the language you work in and copy the first example, usually a simple request that lists your campaigns.
- Test with cURL. A quick request from the terminal confirms that your key works before you write any real code.
- Build your integration. Start small: one scheduled job, one statistics export or one order webhook. Add more once it runs reliably.
If you have not installed wwidgets on your site yet, do that first. Add the pixel code to the head of your site and create your first widget; the getting started guide on our website covers it step by step.
A few good habits for API projects
- Keep keys on the server. Call the API from your back end, a script or an automation tool, never from JavaScript running in the visitor's browser.
- Log what you change. When a script switches widgets on or off, write a short log line so you can see what happened if something looks wrong.
- Use real data only. Send genuine orders to your sales widget. Social proof is only valuable when it is true.
- Respect the request limit. Batch work into scheduled jobs instead of making many calls at once.
FAQ
Do I need an API key for the sales webhook?
No. Your Recent sales widget gives you a webhook address, and you can send orders to it without an API key. The key is only needed for the REST API.
Which plan includes the API?
The API is included in the E-Commerce World plan at €14/month, and you can also use it during the 14-day free trial. See the pricing page for the full plan details.
What is the API request limit?
You can make up to 60 requests per minute. That is enough for typical automation such as schedules, campaign syncing and weekly statistics exports.
We built the developer page so that connecting wwidgets to your store, your reports and your workflows takes minutes rather than hours. Have a look at the developer page, try the examples in the language you prefer and let us know what you build. If you do not have an account yet, start your free trial and get your API key today.
