Skip to content

Gudz SDK

The ERP backend you don't have to build.

Catalog, inventory, orders, warehouses, manufacturing, finance and AI, already built, tested and running real businesses. Install the SDK, keep Gudz as the core, and spend your time on the screens your customers actually see.

$ npm install @gudz/sdk
Get API accessRead the API basics
import { Gudz } from "@gudz/sdk"; const gudz = new Gudz({ apiKey: process.env.GUDZ_API_KEY }); // Your storefront on top, Gudz underneathconst products = await gudz.catalog.list({ channel: "web", inStock: true }); const order = await gudz.orders.create({  customer: { phone: "+91 98100 00000" },  lines: [{ sku: "RC-BAS-05", quantity: 2 }],  payment: { method: "upi" },}); // Stock, picklist, invoice and ledger update on their owngudz.events.on("order.shipped", (e) => notify(e.customer, e.tracking));

What teams build on Gudz

Gudz handles the hard, boring parts of commerce and operations. You build the experience on top.

  • Storefronts and D2C apps

    Your own site or app, with live stock, orders, payments and tracking from Gudz.

    catalogorderspayments

  • POS and retail apps

    Counter billing, returns and store transfers that update stock and books instantly.

    posinventoryeinvoice

  • Field and warehouse apps

    Picker, putaway, audit and sales-rep apps with per-person worker tokens.

    pickingworkersinbound

  • Marketplaces and B2B portals

    Multi-seller catalogs, trade pricing, approvals and credit on one ledger.

    customerspricingledger

  • Your own vertical ERP

    An ERP for your industry, with your workflows and brand, on a proven core.

    every module

  • AI agents

    Give your agents real operations: read stock, draft orders, chase payments, with approvals.

    aimcpevents

Gudz is the core. You own the experience.

Every app you build reads and writes the same record as the Gudz ERP, so your custom screens and Gudz stay in sync without a single integration.

Your apps

Storefront
POS
Field app
Gudz SDK
Typed clientsAuth and rolesWebhooksRealtime
Gudz core
CatalogInventoryOrdersWarehouseManufacturingFinanceCustomersAI agents

Everything an ERP needs, as an API

More than 200 endpoints across every module, with the same rules and permissions the Gudz app uses.

  • gudz.catalog

    Products, variants, bundles, barcodes and media

  • gudz.inventory

    Stock by location, batches, lots and sellable quantity

  • gudz.orders

    B2C and B2B orders, slots, splits and returns

  • gudz.customers

    Accounts, addresses, credit and rate books

  • gudz.pricing

    Price lists, channel prices, discounts and taxes

  • gudz.warehouses

    Locations, zones, bins and the location tree

  • gudz.inbound

    GRNs, quality checks and putaway tasks

  • gudz.picking

    Picklists from orders, scans and pick paths

  • gudz.procurement

    Purchase orders, vendors and rate cards

  • gudz.manufacturing

    BOMs, MRP runs and production orders

  • gudz.ledger

    Journals, payables, receivables and reconciliation

  • gudz.einvoice

    GST invoices, IRNs and e-way bills

  • gudz.payments

    Collections, refunds and payouts

  • gudz.workers

    Operators, shifts and short-lived worker tokens

  • gudz.events

    Webhooks and realtime subscriptions

  • gudz.ai

    Ask Hyperion, run tools and manage approvals

Made for the way developers work

Everything you'd expect from a modern API, and a few things you'd only find after building an ERP the hard way.

  • Typed SDKs

    TypeScript, Python and Go clients with full types and autocomplete.

  • Sandbox workspaces

    A copy of your workspace with test data to build and break things in.

  • Webhooks and realtime

    Signed webhooks for every change, or subscribe to a live stream of events.

  • Safe to retry

    Idempotency keys on every write, so a network blip never counts stock twice.

  • Keys, scopes and tokens

    Scoped API keys, OAuth for partner apps and short-lived worker tokens.

  • CLI and request logs

    Inspect, replay and debug every request from the dashboard or the CLI.

A few lines to your first order

The SDK speaks your business's language: catalog, orders, picklists, ledgers. Here's what it looks like in practice.

import { Gudz } from "@gudz/sdk"; const gudz = new Gudz({ apiKey: process.env.GUDZ_API_KEY }); // Your storefront on top, Gudz underneathconst products = await gudz.catalog.list({ channel: "web", inStock: true }); const order = await gudz.orders.create({  customer: { phone: "+91 98100 00000" },  lines: [{ sku: "RC-BAS-05", quantity: 2 }],  payment: { method: "upi" },}); // Stock, picklist, invoice and ledger update on their owngudz.events.on("order.shipped", (e) => notify(e.customer, e.tracking));

Give any AI model your operations.

The Gudz MCP server exposes your catalog, stock, orders and finance as tools any MCP-compatible model or agent can use, with the same permissions and approvals as a person.

  • Works with Claude, ChatGPT, Cursor and any MCP client
  • Read tools run freely; write tools ask for approval
  • Scoped to the key you connect with

Add Gudz to your MCP client

{  "mcpServers": {    "gudz": {      "command": "npx",      "args": ["-y", "@gudz/mcp"],      "env": { "GUDZ_API_KEY": "gk_live_..." }    }  }}

From zero to live in four steps

  1. 1

    Get a key

    Request access and we'll create a sandbox workspace for you.

  2. 2

    Install the SDK

    npm, pip or go get. Typed from the first line.

  3. 3

    Make your first call

    Create a product, add stock, place an order.

  4. 4

    Go live

    Swap the sandbox key for a production one when you're ready.

Underneath, a plain REST API

Prefer raw HTTP? Every SDK call maps to a documented REST endpoint with an OpenAPI 3.1 spec, a Postman collection and predictable errors.

Base URL
api.delivery.gudz.in/api/v1
Auth
x-api-key header, scoped keys, worker tokens
Spec
OpenAPI 3.1 and a Postman collection
Events
27 signed webhook events, more on the way
Writes
Idempotency-Key header, replays for 24 hours
Lists
Page and limit, with totals
# Every SDK call is a plain REST request underneathcurl -X POST https://api.delivery.gudz.in/api/v1/inventory/adjustments \  -H "x-api-key: $GUDZ_API_KEY" \  -H "Idempotency-Key: adj-hub456-item123-damaged" \  -H "content-type: application/json" \  -d '{"itemId":"item_123","hubId":"hub_456","adjustmentType":"remove","quantity":5,"reason":"damaged"}'

Questions developers ask

Do I need a Gudz ERP subscription to use the SDK?

The SDK runs on a Gudz workspace. You can use the Gudz app alongside your own screens, or run Gudz entirely headless behind your apps.

Is there a sandbox?

Yes. Every developer gets a sandbox workspace with test data, separate keys and no effect on live stock or books.

Can I build an app for other businesses on Gudz?

Yes. Partner apps use OAuth so each business connects its own workspace. Talk to us about listing your app.

How are permissions handled?

Every key and token has scopes, and worker tokens act as a single person with their own permissions, so your apps can never do more than the user could.

Build your next product on Gudz.

Tell us what you're building. We'll set up a sandbox and an engineer to help you ship it.

Get API accessTalk to an engineer