Last reviewed: August 2026 · Reviewed by the MLM Bazaar team
Part of the suite, not a standalone product
API & integrations is one feature of the full MLM software, the channel that connects your core system to the outside world when you need it. You don't buy an API product or a separate integration suite; you buy MLM software and this feature connects it to your gateway, marketplace, or provider as you configure.
Your compensation plan, orders and genealogy tree decide who earns and what was bought. Integrations carry that data out.
Commission management posts, e-wallet & payouts holds, and reports & analytics traces the same entries for one active currency, before any external call.
When you purchase an integration, this feature builds the contract and field mapping per your requirement and, once tested in sandbox, carries the approved payout, order, or notification to Razorpay / Shopify / SMS and similar, quoted per gateway and requirements.
API & integrations is not included by default, every integration is built per your requirement. Core software without external integration is in Rs 19,999 setup + Year 1, see pricing & cost drivers.
Who uses this feature
Built for teams buying MLM software, owners defining an integration need and agencies mapping it for a client, and, once built, for the system channel that carries the approved data to the provider. Members do not configure integrations; future member-scoped API keys expose only their own data when built.
Define which gateway, marketplace or provider you need, choose the single active currency, and test the sandbox handoff (Razorpay, Shopify, SMS etc. as you configure) on a working demo before the integration goes live.
Translate the client's plan + provider requirement into a contract draft, which entities, which fields, which currency, and show the sandbox call and ledger trace on a shareable demo.
When a member-facing API is part of the requirement, a future integration can expose only that member's payouts/orders for the active currency, scoped by role, not the company ledger. No member sees another member's data.
Feature at a glance
Inside your MLM software, API & integrations builds the contract you need and maps fields to the outside system you choose, only when you purchase that integration. Per your requirements, not prebuilt.
Every endpoint you need, members, payouts, orders,
currency with
active_currency, is
defined per your spec, not a fixed product list. Field
names and auth are as you define.
Manual approval is the default when no gateway API is purchased. When you purchase a gateway, approved payouts flow via Razorpay / Paytm / PayPal API (as you configure), quoted per gateway and requirements, and are logged to the same ledger.
Shopify / WooCommerce order sync, SMS / WhatsApp notifications and CRM or KYC calls are each a separately scoped connector, one marketplace or provider at a time, tested in sandbox before production.
Built per your requirements
Every row below is per your requirement, quoted per gateway and requirements, not included by default. You choose which gateway or marketplace the system talks to.
| Integration | What is built | Example providers | Scope |
|---|---|---|---|
| Payment gateway payout | Approved payout → gateway API call + ledger update | Razorpay / Paytm / PayPal as you configure | Quoted per gateway |
| Payment gateway collection | Order fee / fund-request collection confirmation from gateway | Razorpay / Paytm as you configure | Quoted per gateway |
| SMS notifications | Event SMS, payout, order, rank, via your provider + template | SMS provider as you define | Quoted per provider |
| WhatsApp notifications | WhatsApp Business events + templates via your provider | WhatsApp Business API as you define | Quoted per provider |
| Ecommerce sync | Product + order + inventory sync → order volume posts to commission | Shopify / WooCommerce / Magento as you configure | Quoted per marketplace |
| CRM / ERP sync | Member / order / payout push to your CRM or ERP | Zoho / Salesforce / Odoo as you define | Quoted per system |
| KYC / shipping | Verification or shipment status call, data returned to profile/order | KYC API / courier API as you define | Quoted per API |
| Currency rate feed + webhooks |
External rate pull for display +
active_currency in
response; webhooks for payout/order events
|
Rate-feed API / webhook as you configure | Quoted per feed |
No prebuilt connector is shipped by default. Each row is a separately scoped build, quoted per gateway and requirements, sandbox tested before production. Manual approval and single active currency remain the default when no gateway/rate integration is purchased.
Multi-currency, one active at a time
Your installation runs in one active currency at a time, not simultaneous INR+USD wallets. You configure which currency is active, how its rate is set, and, when you purchase the rate/API integration, how the active currency appears outside the wallet. See also e-wallet & payouts for wallet detail, one active currency at a time.
| Configuration | How it works | Example | On demo |
|---|---|---|---|
| Active currency | Admin chooses the single active currency for this installation | Active: INR, or USD, or BTC as you select |
Badge on wallet & ledger +
active_currency
|
| Not simultaneous | Two currencies cannot be active together for one installation | INR and USD wallets at once, Not available | Disclosed |
| Rate source | Display/conversion rate admin-set, or pulled from external rate-feed API when that integration is separately scoped | Admin-set 1 USD = ₹83.50, or external feed as you configure | As you configure |
| Switching | Changing active currency is a configured switch, not a member toggle |
INR → USD re-configured, ledger + future API
active_currency
reflect new currency
|
Shown on request |
| API field |
When an API/rate integration is purchased, responses
carry
active_currency,
consistent with wallet/ledger
|
"active_currency": "INR"
, example field, per your spec
|
Illustrative |
Illustrative response, not live docs{
// Illustrative, per your requirements, not live API docs
"active_currency": "INR",
"rate_source": "admin", // or "external_api" when that integration is purchased
"balances_scoped_to": "single active currency, not simultaneous INR+USD"
}
INR, USD, crypto like BTC and others are available as the
configured single active currency, not as concurrent wallets.
The active_currency JSON field
above is an illustrative example; actual field names are per
your integration spec. Both wallet and future API stay on one
active currency.
Gateway handoff, manual default
Members don't receive commission directly from the gateway, they withdraw from wallets that already hold posted commission. When no gateway integration is purchased, every payout stays manual. When you purchase a gateway, the approved payout uses that gateway's API.
active_currency
consistent
Manual approval is the default on every installation. Automatic bank via gateway API is available only when you purchase that gateway integration, quoted per gateway and requirements, sandbox tested. What you test on the demo is what goes live.
Rules you control
No fixed product defaults, every rule below is per your integration requirement and tested in sandbox.
Razorpay, Paytm, PayPal or as you configure, auth and payout method per your provider, quoted per gateway.
Which MLM fields go to which provider fields, member,
payout, order,
active_currency, per your
spec.
Shopify / WooCommerce / Magento order → MLM order volume and commission trigger, quoted per marketplace, one mapping at a time.
Admin-set rate or external feed + webhook on payout/order, when that feed/hook integration is separately scoped.
Configuration
Defined once from your plan + integration requirement, applied to every call, and re-tested in sandbox before launch. Per your requirements.
Members, payouts, orders, currency and others as you need, which entities are exposed and which fields per entity.
Key / token shape per your spec, when an API is part of the requirement. No default public endpoint.
One gateway at a time per handoff, Razorpay / Paytm / PayPal etc. as you configure, quoted per gateway.
SMS / WhatsApp events, templates, and trigger rules, provider as you choose, quoted per provider.
Single active currency (INR / USD / BTC etc.), admin-set or external feed when that integration is purchased.
Payout / order / currency-change hooks and report exports, as you define, not prebuilt.
Sandbox before production
What you test in sandbox is what goes live, including currency, gateway, and marketplace contract.
Compensation plan + which gateway, marketplace, provider, currency, and which entities need API access.
Entities, field mapping,
active_currency handling,
auth, draft contract per your spec, quoted per gateway.
Sandbox demo seeded with your requirement, single active currency visible, provider in test mode.
Raise a payout / order / notification in sandbox and watch the provider call (gateway/marketplace) not leave sandbox.
Wallet/ledger for
active_currency, payout
history, and illustrative API JSON checked vs your
requirement.
Same member/payout/order appears consistently in reports and wallet, one currency.
Corrections re-tested in same sandbox, not described after the fact.
Only the approved mapping ships. Typical 3 to 7 days when scope and approvals are ready, not a promise.
Visibility
Every wallet debit + illustrative gateway call trace for the active currency, admin sees all, member sees only their data when built.
Request → approval → deductions → provider confirmation →
ledger, with
active_currency consistent.
Per-requirement call log and webhook deliveries, not shipped by default, defined when you purchase the integration.
Related: e-wallet & payouts (one active currency), commission management, reports & analytics.
Proof, not promises
Every claim below is illustrative until a live integration is purchased, then your sandbox replaces the illustration.
External services connect to the MLM Bazaar core as configured, with each gateway or connector separately scoped and quoted.
Integrations are configured and tested in a sandbox before deployment to the live system.
One active currency at a time, admin-set or external rate-feed when that integration is separately scoped.
Pricing & scope
API & integrations is not included by default, every endpoint and connector is built per your requirements.
active_currency etc.,
spec per requirement
Kick-off
To define the contract and quote per gateway and requirements:
Common questions
It is a feature inside MLM Bazaar MLM software that connects your core system, genealogy, commission engine, wallets and reports, to external systems you choose. Nothing is prebuilt or included by default. Every endpoint, gateway, or connector is built per your requirements and quoted per gateway and requirements, then tested in a sandbox on a working demo before it goes live.
No public API is configured by default today. API endpoints are built per your integration spec, which entities to expose (members, payouts, orders, currency) and which fields to map, and are defined before any gateway or marketplace work begins. Illustrative examples on this page show planned contracts, not live documentation.
Manual approval is the default when no gateway API is purchased. When you purchase a gateway integration, Razorpay, Paytm, PayPal and similar as you configure, the flow is: member request → admin approval/hold → deductions as you configure → gateway API call (sandbox tested) → ledger and payout history recorded. Each gateway is quoted per gateway and requirements.
You can configure any single currency to be active, INR,
USD, BTC and others as you need, but two currencies
cannot be active at the same time for one installation.
The active currency applies to wallets, ledger, payouts,
and, when you purchase the rate/API integration, to the
API response as
active_currency (example
field name, per your spec). Rate can be admin-set or
pulled from an external rate-feed API when that
integration is separately scoped.
Shopify, WooCommerce, Magento, OpenCart and similar ecommerce sync is built per your requirements, product and order sync that posts order volume to the commission engine. There is no prebuilt Shopify connector shipped by default; each marketplace connector is separately scoped and quoted per marketplace and requirements, then tested on the demo.
No. SMS and WhatsApp Business API integrations, events like payout, order, rank, or join, are built per your requirements with your chosen provider and templates. Each provider integration is separately scoped and quoted per gateway and requirements, not included in the Rs 19,999 setup + Year 1 core software.
Payment gateway payout (Razorpay, Paytm, PayPal as you configure), ecommerce (Shopify, WooCommerce as you configure), SMS/WhatsApp, CRM/ERP (Zoho, Salesforce, Odoo as you define), KYC verification, shipping/courier, and external currency rate feeds. CRM/ERP, KYC, and shipping are also per requirement, separately scoped.
An API is the endpoint or contract MLM Bazaar builds to expose or accept data (members, payouts, orders, currency) as you define. An integration is the gateway or marketplace connection that uses that contract, Razorpay for auto-payout, Shopify for order sync, or a rate-feed for currency. Both are built per your requirements and quoted per gateway and requirements; neither is prebuilt.
Yes, but it is a scoped update, new gateway or marketplace is configured on a sandbox demo, field mapping and currency handling re-tested, then moved to production. What you test in sandbox is what goes live. Each change is quoted per gateway and requirements.
API & integrations is not included by default, it is built per your requirements when you need it. Core MLM software without external integration is included in the Rs 19,999 setup + Year 1. Every API endpoint and every integration, payment gateway, ecommerce, SMS/WhatsApp, CRM/ERP, rate feed, is separately scoped and quoted per gateway and requirements. From Year 2, hosting, domain and support renew annually per the service agreement. Exact wording must match the service agreement.
Share your plan + requirement. We define the contract, configure the sandbox with one active currency, and you test the gateway, marketplace and rate call, quoted per gateway, before it goes live.
Chat on WhatsApp Call UsTypical demo to production 3 to 7 days when scope and approvals are ready, not a promise. Includes manual payouts until a gateway API is purchased.