New: Application API docs
Pick the API you are reading here — the Merchant API for your own store, the Application API for partner apps.
Everything you need to integrate with the Gini v2 Third-Party API.
The API uses conventional HTTP status codes and returns a JSON body describing the problem. A 2xx status means success, 4xx means the request was rejected, and 5xx means something failed on our side.
Authentication failures and a few read lookups return an error key; validation and most controller errors return a message key (validation errors also include a field-keyed errors object).
{
"error": "Invalid signature"
}
{
"message": "The given data was invalid.",
"errors": {
"price": [
"The price must be at least the configured minimum."
]
}
}
| Code | Meaning |
|---|---|
| 200 OK | The request succeeded. |
| 201 Created | A resource was created (create endpoints). |
| 202 Accepted | An async job was queued (exports). |
| 400 Bad Request | A malformed request or an illegal order status transition. |
| 401 Unauthorized | Missing, expired, or invalid signature or API key. |
| 403 Forbidden | The API account is inactive. An HTML page instead of JSON means the edge blocked the request before it reached the API — see Troubleshooting. |
| 404 Not Found | The resource does not exist or does not belong to you. |
| 409 Conflict | A retry arrived while the first request with the same Idempotency-Key was still running. |
| 422 Unprocessable | Validation failed or a business rule blocked the action. |
| 429 Too Many Requests | You exceeded the rate limit — see Rate limiting. |
| 500 Server Error | An unexpected error on our side. |