تاجر جني
Which API?
Merchant API For merchants: manage your own catalogue, orders and finances through the v2 Third-Party API. Application API For partner apps: browse Gini merchants and products, send customers to checkout and follow their orders.

New: Application API docs

Pick the API you are reading here — the Merchant API for your own store, the Application API for partner apps.

Merchant dashboard
Getting started
Introduction

Application API

For partner applications: browse merchants and products, hand customers a checkout link, and follow the orders it creates.

Introduction

The API for partner applications. Each application is issued an app_id + app_secret pair and, optionally, a whitelist of the merchants it may reach. Every request is authenticated with an HMAC-SHA256 signature computed from the request and your app_secret.

This is the application API, for partner apps that list Gini merchants and send customers to checkout. If you are a merchant integrating your own store, you want the Merchant API instead — it is a different API with different endpoints and signing rules.
Base URL

All responses are JSON, and every endpoint requires authentication. Every path in this reference hangs off this base.

The path you sign includes the /api/... prefix, e.g. /api/third-party/v1/applications/products — not just /products.
Endpoints
# Method Path Purpose
1 GET /merchants Your merchants, searchable, optionally nearest-first
2 GET /products Product search and browse
3 GET /products/{slug} One product
4 GET /categories Category tree with nested subcategories
5 GET /sub-categories Flat, paginated subcategories
6 GET /reels Shuffled reel feed
7 POST /checkout-tokens Seal a basket into a checkout link
8 GET /orders Orders created through your application
9 GET /orders/{id} One order
10 POST /orders/{id}/cancel Cancel a pending order
11 GET /reject-reasons Reasons accepted by the cancel endpoint
12 GET /states States and districts, for address pickers

Plus order webhooks that we send to you.

Using an AI assistant?
Every endpoint is also available as a tool on our MCP server — connect Claude (claude.ai, Desktop or Code) or any MCP client with your app_id and app_secret, and it signs each call for you.
Getting started
1

Get your credentials. Gini issues your application an app_id and app_secret, and tells you which merchants, payment methods and grants it has.

2

Sign every request. Attach X-API-KEY, X-TIMESTAMP and X-SIGNATURE as described in Authentication — remember to sign the canonical query string.

3

Call the API. Start with a signed GET to /categories to confirm your signature works, then browse /merchants and /products and issue your first checkout token.