Developers

Build on Dhru.Plug in anything.

Plain HTTP contracts for suppliers, resellers, and payments. One MCP address that teaches them to your AI. Open starter kits.

A laptop showing a nine-line supplier endpoint beside a Dhru Fusion order: Fusion posts the order to the endpoint, it answers 200 with a code, and the order is delivered

Developer MCP

One address.
Your AI knows the rest.

Add it to Claude Code, Cursor, or ChatGPT. Your AI reads the real contracts, writes the integration, and checks every payload.

Try one

https://www.dhru.com/mcp

Run this once in your terminal.

claude mcp add --transport http dhru-developers https://www.dhru.com/mcp
  • No sign-in
  • Read-only
  • Dhru Fusion Pro
  • PayerOne
  • Dhru Fusion API standards

Dhru Fusion APIs

Four contracts.Plain HTTP.

No SDK to learn. Each one is a few requests you can read in a minute.

Fusion sends the order to your URL.

Dhru FusionYour server

POST /fulfil HTTP/1.1Host: your-server.comContent-Type: application/x-www-form-urlencodedโ€‹Email=maya%40example.com
  • Any HTTPS endpoint
  • GET, POST, PUT, PATCH or DELETE
  • Up to 3 retries per supplier
  • Catalog and price import

Under the hood

The details, handled.

Order fields

Typed, and checked for you.

  • Text, number, email, dropdown, file
  • Required and limits
  • Sent to suppliers by name

Retries & failover

A supplier fails. The order doesn't.

  • 1 to 3 retries
  • Backup supplier on error
  • Professional and up

Catalog import

Pull in a supplier's catalog.

  • Products and prices
  • Order fields included
  • Sync when you choose

API tokens

One token, one currency.

  • Expiry date
  • IP allowlist
  • Up to 4 per client

Order limits

Caps you set for each client.

  • Per hour or per day
  • By channel
  • HTTP 429 when reached

Telegram

Your own bots, and a Mini App.

  • Staff alerts
  • Client notifications
  • Orders inside Telegram

PayerOne API

Take a payment with one request.

Create an order, send the customer to the hosted checkout, and fulfil only when the signed notification arrives.

  1. 01

    Create. Post the amount and your own order reference.

  2. 02

    Redirect. Send the customer to the checkout page you get back.

  3. 03

    Verify. Check the signature on the notification, then fulfil.

  • USDT, USDC and Bitcoin
  • Your own gateway accounts
  • Priced in USD, EUR, GBP or USDT
  • Live and sandbox keys
POST /checkout/v1/orders_v2 HTTP/1.1Host: api.payerone.comAuthorization: Bearer YOUR_API_KEYContent-Type: application/jsonโ€‹{  "amount": 25.00,  "currency_code": "USD",  "description": "Order 1048",  "customer_name": "Maya R.",  "customer_email": "maya@example.com",  "custom_id": "1048",  "ipn_url": "https://your-site.com/hooks/payerone",  "success_url": "https://your-site.com/thanks",  "fail_url": "https://your-site.com/cart"}

Starter kits

Start from working code.

Each kit is a small, readable repository. Clone it and change what you need.

fusion-pro-simple-api-request-listener

Supplier listener

A listener Fusion can import a catalog from and send orders to.

  • PHP

fusion-pro-simple-url

One-URL supplier

The smallest supplier there is: one endpoint that fulfils an order.

  • PHP

reseller-api

Reseller API

Account, catalog, orders and callback receivers, ready to run.

  • PHP 8.1+
  • Node.js 18+
  • Postman

payment-gateway-development-kit

Payment gateway

A provider-neutral scaffold for connecting your own payment provider.

  • PHP

FAQ

Before you build.

What is the developer MCP?

A public address your AI coding tool can connect to. It gives the tool the real contracts, starter code, and payload checks for Dhru Fusion Pro, PayerOne, and the Dhru Fusion API standards. It is read-only, needs no sign-in, and cannot see or change any store or account.

Do I need a particular plan to use the APIs?

The Supplier API, the Reseller API, and custom payment gateways are part of every Dhru Fusion plan. Backup-supplier failover and AI connected apps come with Professional and Enterprise.

Is there a sandbox?

Not for the Fusion APIs. A Reseller API order is a real, paid order, so test with a small product in a test client account. Payment providers have their own sandboxes, and PayerOne gives you sandbox keys.

How do I know a callback is genuine?

An order callback from Fusion is a notice and carries no signature, so confirm the result with an authenticated order lookup before you release anything. PayerOne notifications are signed with HMAC SHA-256; check the signature against the raw body.

Can an AI app change my store?

Not through the developer MCP: it is read-only. A store's own AI connector is separate and needs a staff sign-in. There, sensitive changes are two-step: the first call only returns a preview, and nothing is applied until that exact request is confirmed. It works inside the staff member's role, cannot delete data, and every call is logged.

Which languages do the kits use?

The supplier and payment gateway kits are PHP. The Reseller API kit has PHP and Node.js examples and a Postman collection. The contracts are plain HTTP, so any language works.

Is there an API for Dhru Alpha?

Dhru Alpha does not have a public API today. It connects to ChatGPT and Claude through a read-only connector, and it imports and exports data as CSV and Excel files.

Ready to build?

Start a Fusion store, connect your first supplier, and take a live order.