تاجر جني
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
Resources
Rate limiting

API documentation

Everything you need to integrate with the Gini v2 Third-Party API.

Getting started API reference Store API Finance API Settings API Insights API Wholesale API Resources
MCP server Endpoint summary Error responses Rate limiting Changelog

Rate limiting

Requests are throttled per API account to keep the platform stable. Stay under the limits and you will never notice them; exceed one and you get a 429 until the window resets.

Limits
Scope Limit
All Third-Party endpoints 60 requests per minute, per API account
Webhook endpoints An extra 5 requests per minute on top of the shared limit
When you hit the limit

A throttled request returns 429 Too Many Requests with a Retry-After header telling you how many seconds to wait. Every response also carries the standard rate-limit headers so you can back off before you hit the wall.

Response headers 
HTTP/1.1 429 Too Many Requests
Retry-After: 42
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 0
Notes
  • The webhook management endpoints (get, update, delete, test) share the 60/min budget and add their own 5/min cap — space out webhook test calls.
  • Watch X-RateLimit-Remaining and slow down as it approaches zero instead of waiting for a 429.
  • When you receive a 429, honor Retry-After before retrying — retrying immediately just extends the throttle window.
  • Limits are per API account (your API key), not per IP, so spreading calls across servers does not raise them.
Previous Error responses Next Changelog