Quick Answer
Can Beejek integrate with a custom or non-standard POS?
Yes. If your POS isn't one of Beejek's native integrations, you can use the Beejek REST API to send transaction data directly. Any system that can make an HTTP POST request can trigger WhatsApp receipts, smart reminders, and retention automations.
What Custom API doesn't do
The gap Beejek fills
Your POS or ERP handles transactions well. But after each sale, the customer relationship exists only in a database. There's no automated follow-up channel. No way to deliver a receipt they'll actually see. No systematic retention automation that runs without manual effort. The transaction data is there — the engagement layer is missing.
What Beejek unlocks after every Custom API sale
Every capability below runs automatically from the moment you connect. No manual management, no separate systems.
Digital Receipts
Any POS or system can trigger a WhatsApp receipt — one API call
POST a transaction to the Beejek REST API — customer phone number, merchant ID, amount, currency, and optional line items — and a branded WhatsApp receipt fires within 2 seconds. The API schema is simple, documented, and requires no specialised integration framework. Any system that can make an outbound HTTP request can connect.
A merchant running a custom-built POS had their developer integrate the Beejek API in a single day — and was delivering WhatsApp receipts to customers the following morning.
Smart Reminders
Your custom POS transaction data drives Beejek's full retention automation
Every transaction POSTed to the Beejek API is tracked in the customer timeline. At 30 days without a new transaction, Smart Reminders fire automatically. At 90 days, the second message goes out. The full retention engine runs from your custom POS data — no additional API calls required after the initial transaction POST.
Businesses running proprietary or bespoke POS systems get the same Smart Reminder capability as Loyverse or Lightspeed merchants — driven by their own transaction data.
Google Review Automation
Post-sale review automation — triggered by your custom POS transactions
Every transaction POSTed to the Beejek API triggers the same automated post-sale sequence as a native integration: NPS survey at 2 hours, Google review request for Promoters. Smart suppression excludes unhappy customers. Your Google rating benefits from every custom POS sale — not just native integration sales.
Custom POS merchants build their Google review volume automatically from the same transaction stream that powers their receipts and reminders.
Broadcast Campaigns
Your custom POS customer base, ready for WhatsApp campaigns
Every customer whose transaction was POSTed to the Beejek API is in your broadcast list — filterable by transaction date, frequency, and spend. Launch a promotional campaign to your full customer base from the Beejek dashboard without any additional API work.
Custom POS merchants have the same full broadcast campaign capability as Loyverse or Shopify merchants — the audience is built automatically from the transaction stream.
Analytics
Retention analytics from any transaction source
Transactions POSTed from your custom POS flow into the same Beejek analytics dashboard as native integrations. New vs returning customer ratios, NPS trends, and campaign ROI are all available — regardless of which system generated the original transaction.
The Beejek analytics layer works on top of any POS or ERP — giving merchants with proprietary systems the same retention visibility as those using Loyverse or Lightspeed.
How to connect Custom API
Sign up and get your API credentials
Create a Beejek account and retrieve your API endpoint and key from the dashboard. A sandbox environment is available immediately for testing.
POST transaction data on each sale
When a sale completes in your system, POST the transaction details to the Beejek API. The payload schema is simple — at minimum: customer phone, merchant ID, amount, and currency. Full documentation is provided on sign-up.
Beejek handles everything after that
WhatsApp receipts fire instantly. Smart Reminders start tracking. NPS surveys, Google Reviews, and all automations queue — exactly as with a native integration. No further API calls required for the retention automation.
A day in the life
What happens in Custom API and what happens on your customer's phone — simultaneously.
What changes after you connect Custom API
Measurable outcomes from the first sale after connection.
1 day
Typical dev time
For a developer to integrate a custom POS with the Beejek REST API.
All
Features unlocked
The full Beejek stack — from a single HTTP POST endpoint.
98%
WhatsApp open rate
Regardless of which POS or system generated the original transaction.
330×
Smart Reminder ROI
Available to any merchant — regardless of POS or ERP system.
“Our POS is custom-built. The Beejek API was straightforward to integrate — our developer had it working in a day.”
A retailer with a custom POS system
Included in your plan
Pro
Unlimited stores · All features · Custom API integration included
Per-message charges apply. Utility messages from $0.003. Setup fee covers onboarding & configuration.
Frequently asked questions
At minimum: customer phone number, merchant identifier, transaction amount, and currency. Optional fields include line items (for the receipt display), customer name, and transaction reference number. Full API documentation is provided on sign-up.
Yes. Beejek provides a test environment with a sandbox API key. Test messages are sent to a designated test number — not to real customers. You can validate the full integration before going live.
Yes. Any system that can make an outbound HTTP POST request — regardless of whether it's cloud-based, on-premise, or legacy — can integrate with the Beejek API.
Yes. API documentation is available on request. Contact the Beejek team via WhatsApp to request early access to documentation before creating an account.
Most developers complete a working integration in 1–2 days. The API is a single endpoint with a straightforward JSON payload — no SDK or specialised library required.
Beejek can deliver webhook callbacks to your system on key events — such as WhatsApp delivery confirmation, NPS response received, and payment confirmed. Callback configuration is available in the Beejek dashboard.
The initial POST should include all available data. If a transaction needs to be updated (e.g., a refund or cancellation), a separate refund endpoint accepts the transaction reference and triggers a refund receipt automatically.
Beejek uses idempotent transaction IDs — if the same transaction reference is POSTed twice, Beejek processes it only once. For failed API calls, Beejek recommends retrying with the same transaction reference using exponential backoff. A sandbox environment is available for testing failure scenarios.
Other integrations
Connect Custom API to Beejek
Setup takes Developer integration. No developer required. Cancel any time.
No credit card required · Setup in 2 minutes