Mgn-Estore. Com Public API Documentation

Mgn-Estore.com- Official Game Store and Top-Up Services

Base URL: https://mail.mgn-estore.com/api/v1 Support: @B_na_MGN

API key not verified Use GET /getMe to verify and auto-load your webhook secret.

Introduction

Integrate voucher and top-up products into your own system using Mgn-Estore.com public JSON API. This page includes live playground blocks so resellers can verify their API key, test requests, inspect raw request bodies, and validate webhook signatures directly from the browser.

REST + JSON Live Playground Idempotent Orders Signed Webhooks Top-up Validation DZD

Base URL: https://mail.mgn-estore.com/api/v1

Catalog flow Use /games, /categories, and /products to build your browsing and purchase flow.

Safe order creation Use X-Idempotency-Key for retries and optionally send callback_url plus callback_mode.

Webhook modes legacy sends final updates only. events sends signed status-change webhooks.

Base URL & Versioning

All endpoints below are relative to https://mail.mgn-estore.com/api/v1.

Version v1 is stable. Future breaking versions should use a separate prefix.

Authentication

Authenticated endpoints require your personal API key in the request header below:

X-API-KEY: YOUR_API_KEY

Security note: Keep your API key on your backend only. Do not expose it inside public frontend code or mobile app bundles.

Idempotency

For order creation, send X-Idempotency-Key with a unique UUID. Reusing the same key with the same payload safely returns the same order instead of creating duplicates.

X-Idempotency-Key: 550e8400-e29b-41d4-a716-446655440000

Get Account Details

Retrieve reseller profile data, balance, currency, and personal webhook_secret.

GET https://mail.mgn-estore.com/api/v1/getMe

Auth: X-API-KEY 200

curl -s "https://mail.mgn-estore.com/api/v1/getMe" \
  -H "X-API-KEY: YOUR_API_KEY" \
  -H "Accept: application/json"

{
  "success": true,
  "data": {
    "user_id": 579365494,
    "username": "reseller_pro",
    "balance": "1250.5000",
    "webhook_secret": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "currency": "DZD"
  }
}

Request

No request yet.

Response—

Response will appear here.

Games

List available games that can be used to group or filter top-up products.

GET https://mail.mgn-estore.com/api/v1/games

Public 200

curl -s "https://mail.mgn-estore.com/api/v1/games" -H "Accept: application/json"

{
  "success": true,
  "data": [
    {
      "id": 1,
      "name": "PUBG Mobile"
    },
    {
      "id": 2,
      "name": "Mobile Legends"
    }
  ]
}

Request

No request yet.

Response—

Response will appear here.

Query	Type	Required	Description
`game_id`	integer	NO	Filter categories for a specific game.

Products

List active products. Supports filters such as type, game, category, and IDs.

GET https://mail.mgn-estore.com/api/v1/products

Public 200

Query	Type	Required	Description
`type`	string	NO	`voucher` or `topup`
`game`	string	NO	Search by game name
`category`	string	NO	Search by category name
`game_id`	integer	NO	Filter by game ID
`category_id`	integer	NO	Filter by category ID
`page`	integer	NO	Page number
`per_page`	integer	NO	Maximum 100

curl -s "https://mail.mgn-estore.com/api/v1/products?type=voucher&per_page=10" \
  -H "Accept: application/json"

{
  "success": true,
  "data": [
    {
      "id": 55,
      "name": "Steam Wallet 10 USD",
      "game_id": 0,
      "game": "",
      "category_id": 3,
      "category": "Gift Cards",
      "type": "VOUCHER",
      "price": "9.9900",
      "stock_status": "FINITE",
      "stock_count": 120,
      "fields": [],
      "supports_player_validation": false
    }
  ],
  "meta": {
    "total": 1,
    "per_page": 10,
    "current_page": 1,
    "last_page": 1
  }
}

type

per_page

game

Validate Player

Validate the target player before creating a top-up order. This endpoint is only relevant for products that require player input.

POST https://mail.mgn-estore.com/api/v1/validate-player

Auth: X-API-KEY 200

Field	Type	Required	Description
`product_id`	integer	YES	Active top-up product ID
`player_id`	string	YES	Player or user identifier
`server_id`	string	NO	Server/zone/region value when needed
`input_2...input_8`	string	NO	Extra mapped input fields for advanced products

curl -s "https://mail.mgn-estore.com/api/v1/validate-player" \
  -X POST \
  -H "X-API-KEY: YOUR_API_KEY" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "product_id": 91,
    "player_id": "5123456789",
    "server_id": "2001"
  }'

{
  "success": true,
  "data": {
    "nickname": "PlayerOne",
    "player_name": "PlayerOne",
    "region": "TR",
    "server_id": "2001",
    "nickname_verified": true,
    "validation_optional": false
  }
}

product_id

player_id

server_id

extra JSON

Request

No request yet.

Response—

Response will appear here.

Create Order

Create a voucher or top-up order. For top-up products, validate the player first when required. Use X-Idempotency-Key to avoid duplicates on retries.

POST https://mail.mgn-estore.com/api/v1/order

Auth: X-API-KEY 200

Field	Type	Required	Description
`product_id`	integer	YES	Target product ID
`qty`	integer	NO	Voucher quantity. Top-up orders must use `1`.
`player_id`	string	TOPUP	Required for top-up products
`server_id`	string	NO	Optional second field for supported games
`input_2...input_8`	string	NO	Additional mapped inputs
`callback_url`	string	NO	HTTPS webhook endpoint
`callback_mode`	string	NO	`legacy` (default) or `events`

Headers

X-API-KEY: YOUR_API_KEY
X-Idempotency-Key: 550e8400-e29b-41d4-a716-446655440000

Voucher order example

{
  "product_id": 55,
  "qty": 2,
  "callback_url": "https://yourdomain.com/webhooks/mgn-estorecom",
  "callback_mode": "legacy"
}

Top-up order example

{
  "product_id": 91,
  "qty": 1,
  "player_id": "5123456789",
  "server_id": "2001",
  "callback_url": "https://yourdomain.com/webhooks/mgn-estorecom",
  "callback_mode": "events"
}

Response

{
  "success": true,
  "data": {
    "order_id": 8821,
    "status": "PENDING",
    "player": {
      "nickname": "PlayerOne",
      "player_name": "PlayerOne",
      "region": "TR",
      "server_id": "2001",
      "nickname_verified": true
    }
  }
}

product_id

qty

player_id

server_id

callback_url

callback_mode

X-Idempotency-Key

extra JSON

Tip: Leave callback_mode as legacy for old integrations. Use events only if your webhook consumer is ready for PENDING, PROCESSING, COMPLETED, and FAILED status updates.

Request

No request yet.

Response—

Response will appear here.

Get Order Status

Fetch a single order by ID.

GET https://mail.mgn-estore.com/api/v1/order/{id}

Auth: X-API-KEY 200

curl -s "https://mail.mgn-estore.com/api/v1/order/8821" \
  -H "X-API-KEY: YOUR_API_KEY" \
  -H "Accept: application/json"

{
  "success": true,
  "data": {
    "order_id": 8821,
    "client_order_id": "7b8f0a64-4f7e-4a2f-9a0a-7b1f0a3bfa11",
    "player_id": "5123456789",
    "server_id": "2001",
    "player_name": "PlayerOne",
    "region": "TR",
    "player": {
      "nickname": "PlayerOne",
      "player_name": "PlayerOne",
      "region": "TR",
      "server_id": "2001",
      "nickname_verified": true
    },
    "status": "COMPLETED",
    "price": "19.9800",
    "support_status": "waiting_reseller",
    "support_needs_reply": true,
    "support_unread_messages": 1,
    "conversation": {
      "id": 55,
      "status": "waiting_reseller",
      "requires_reply": true,
      "unread_messages": 1,
      "last_message_at": "2026-09-27T15:38:00+04:00",
      "messages": [
        {
          "id": 102,
          "sender": "support",
          "message": "Please ask the customer for the verification code.",
          "created_at": "2026-09-27T15:38:00+04:00"
        }
      ]
    },
    "created_at": "2026-01-30T13:05:04+00:00"
  }
}

order_id

Request

No request yet.

Response—

Response will appear here.

Messages de commande

Utilisez les messages de commande lorsque le support a besoin d'informations supplémentaires du client final. Le client API peut lire la conversation dans la réponse de la commande et renvoyer la réponse du client via l'API.

Les réponses de commande incluent support_status, support_needs_reply, support_unread_messages et la conversation la plus récente.
GET /order/{id} inclut toujours la conversation la plus récente. Le polling reste donc disponible si un webhook est manqué ou si aucune callback URL n'a été fournie.
Traitez les messages de commande comme des données sensibles en transit. Ne journalisez pas le contenu des messages et ne stockez pas de mots de passe ni d'identifiants longue durée. Utilisez uniquement les informations nécessaires à la commande concernée.

POST https://mail.mgn-estore.com/api/v1/order/{id}/reply

Auth: X-API-KEY 200

Répond à la dernière conversation de support ouverte pour cette commande. Si conversation_id est fourni, il doit appartenir à la même commande.

Field	Type	Required	Description
`message`	string	YES	Réponse du client ou information spécifique à la commande demandée pour la terminer. Maximum 3000 caractères.
`conversation_id`	integer	NO	Identifiant de conversation facultatif renvoyé par GET /order/{id}.

curl -s -X POST "https://mail.mgn-estore.com/api/v1/order/8821/reply" \
  -H "X-API-KEY: YOUR_API_KEY" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "conversation_id": 55,
    "message": "Customer response"
  }'

{
  "success": true,
  "data": {
    "order_id": 8821,
    "conversation": {
      "id": 55,
      "status": "reseller_replied",
      "requires_reply": false,
      "unread_messages": 0,
      "last_message_at": "2026-09-27T15:40:00+04:00",
      "messages": [
        {
          "id": 102,
          "sender": "support",
          "message": "Please ask the customer for the verification code.",
          "created_at": "2026-09-27T15:38:00+04:00"
        },
        {
          "id": 103,
          "sender": "client",
          "message": "Customer response",
          "created_at": "2026-09-27T15:40:00+04:00"
        }
      ]
    }
  }
}

order_id

conversation_id

message

Request

No request yet.

Response—

Response will appear here.

List Orders

Retrieve your recent order list.

GET https://mail.mgn-estore.com/api/v1/orders

Auth: X-API-KEY 200

{
  "success": true,
  "data": [
    {
      "order_id": 8821,
      "client_order_id": "7b8f0a64-4f7e-4a2f-9a0a-7b1f0a3bfa11",
      "player_name": "PlayerOne",
      "region": "TR",
      "player": {
        "nickname": "PlayerOne",
        "player_name": "PlayerOne",
        "region": "TR",
        "server_id": "2001",
        "nickname_verified": true
      },
      "status": "COMPLETED",
      "price": "19.9800",
      "support_status": "waiting_reseller",
      "support_needs_reply": true,
      "support_unread_messages": 1,
      "created_at": "2026-01-30T13:05:04+00:00"
    }
  ]
}

Request

No request yet.

Response—

Response will appear here.

Webhooks

If you send a valid callback_url while creating an order, webhook behavior depends on callback_mode.

Mode	Behavior
`legacy`	Backward-compatible mode. Only one final reseller webhook is sent when the order reaches `COMPLETED` or `CANCELED`.
`events`	Status-change mode. Signed webhooks are sent for public lifecycle changes such as `PENDING`, `PROCESSING`, `COMPLETED`, and `FAILED`. En mode events, des callbacks signés sont aussi envoyés pour les nouveaux messages du support avec l'événement order.message.

Voucher orders may finalize very quickly.
Top-up orders may remain in PROCESSING before completion.
Event mode is best for automation flows that should react before final completion.
When an order is later completed or canceled from the admin panel, the same saved callback_url is used for the final webhook.
Your webhook endpoint should answer with 2xx quickly and tolerate duplicate deliveries.

Signature Verification

Signed webhook requests include an HMAC header generated using your personal webhook_secret from /getMe.

Header	Description
`X-GAMEX-Signature`	HMAC SHA-256 of the raw request body in format `sha256=...`
`X-GAMEX-Event`	Type d'événement. Les valeurs actuelles sont order.status_changed et order.message.
`Content-Type`	`application/json`

$secret = 'YOUR_WEBHOOK_SECRET';
$payload = file_get_contents('php://input');
$signature = $_SERVER['HTTP_X_GAMEX_SIGNATURE'] ?? '';

$computed = 'sha256=' . hash_hmac('sha256', $payload, $secret);

if (!hash_equals($computed, $signature)) {
    http_response_code(401);
    exit('Invalid signature');
}

http_response_code(204);

Signature Tester Client-side

webhook_secret

payload

X-GAMEX-Signature

Computed Signature

No calculation yet.

Verification Result—

Result will appear here.

Payload Examples

Legacy final webhook example

{
  "event_id": "47c8c6ba-16a5-4089-9f62-7ae1e51d4c0f",
  "order_id": 8821,
  "client_order_id": "7b8f0a64-4f7e-4a2f-9a0a-7b1f0a3bfa11",
  "status": "COMPLETED",
  "product_name": "Steam Wallet 10 USD",
  "qty": 2,
  "player_id": null,
  "player_name": null,
  "server_id": null,
  "region": null,
  "player": [],
  "price": "19.9800",
  "currency": "DZD",
  "delivery": ["CODE_1", "CODE_2"],
  "timestamp": "2026-01-30T13:05:10+00:00"
}

Events mode webhook example

{
  "event": "order.status_changed",
  "callback_mode": "events",
  "order_id": 8821,
  "client_order_id": "7b8f0a64-4f7e-4a2f-9a0a-7b1f0a3bfa11",
  "product_id": 91,
  "product_name": "PUBG Mobile 60 UC",
  "product_type": "TOPUP",
  "game_id": 1,
  "game_name": "PUBG Mobile",
  "player_id": "5123456789",
  "player_name": "PlayerOne",
  "server_id": "2001",
  "region": "TR",
  "player": {
    "nickname": "PlayerOne",
    "player_name": "PlayerOne",
    "region": "TR",
    "server_id": "2001",
    "nickname_verified": true
  },
  "qty": 1,
  "price": "0.8800",
  "status": "PROCESSING",
  "message": "Order is currently being processed.",
  "timestamp": "2026-03-30T02:00:00+00:00"
}

Exemple de webhook de message de commande

{
  "event": "order.message",
  "callback_mode": "events",
  "order_id": 8821,
  "client_order_id": "7b8f0a64-4f7e-4a2f-9a0a-7b1f0a3bfa11",
  "product_id": 91,
  "product_name": "PUBG Mobile 60 UC",
  "conversation_id": 55,
  "message_id": 102,
  "sender": "support",
  "target_type": "reseller",
  "message": "Please ask the customer for the verification code.",
  "requires_reply": true,
  "created_at": "2026-09-27T15:38:00+04:00",
  "timestamp": "2026-09-27T15:38:00+04:00"
}

Traitez les messages de commande comme des données sensibles en transit. Ne journalisez pas le contenu des messages et ne stockez pas de mots de passe ni d'identifiants longue durée. Utilisez uniquement les informations nécessaires à la commande concernée.

Order Status Lifecycle

Status	Description	Where used
`PENDING`	Order created and waiting for provisioning.	Event mode public webhook
`PROCESSING`	Provisioning started but not finalized yet.	Order responses and event mode webhooks
`COMPLETED`	Order delivered successfully.	All modes
`CANCELED`	Internal final failure state used by legacy/final flows.	Legacy final callbacks and order views
`FAILED`	Public failure name used by event mode webhook payloads. Treat it as a terminal canceled/failed order.	Events mode public webhook

Error Codes

Use error.code for programmatic handling.

{
  "success": false,
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "player_id is required."
  }
}

VALIDATION_ERROR Input, quantity, product, or field validation failed.

INSUFFICIENT_FUNDS Wallet balance is too low for the requested order.

VALIDATION_REQUIRED Top-up character validation must be completed before ordering.

IDEMPOTENCY_CONFLICT The same idempotency key was reused with a different payload.

SECURITY_ERROR Callback URL is invalid, unsafe, or rejected by SSRF protection.

SERVICE_ERROR External validation or provisioning service is temporarily unavailable.

CONVERSATION_NOT_FOUND Le conversation_id fourni n'appartient pas à cette commande.

CONVERSATION_CLOSED La conversation sélectionnée est déjà résolue ou fermée.

FEATURE_DISABLED La messagerie de commande est temporairement désactivée par la plateforme.

Changelog

2026-09-27 Ajout des conversations de commande Public API, de l'endpoint de réponse client, des champs de polling de secours et des webhooks signés order.message.

2026-05-14 Final events webhooks are now dispatched when orders are completed or canceled after creation, including admin/manual status changes. Legacy webhook payload documentation was aligned with the stable payload shape.

2026-03-30 Added callback_mode documentation, event-style webhook coverage, signed status-change payload examples, and dynamic project branding from admin settings.

Mgn-Estore. Com Public API Documentation

Introduction

Base URL & Versioning

Authentication

Idempotency

Get Account Details

Games

Categories

Products

Validate Player

Create Order

Headers

Voucher order example

Top-up order example

Response

Get Order Status

Messages de commande

List Orders

Webhooks

Signature Verification

Payload Examples

Legacy final webhook example

Events mode webhook example

Exemple de webhook de message de commande

Order Status Lifecycle

Error Codes

Changelog