Smile API Documentation

Base URL

API Base URL

https://demo.shalsmileapi.site/api

All API endpoints are relative to this base URL. Make sure to include the /api prefix in all requests.

Balance Endpoints

Get Smile account balance for all regions or a specific region.

GET /balance

Get Smile account balance from all configured regions (BR, PH).

Example Request

HTTP

GET /api/balance

Example Response

JSON

{
  "success": true,
  "message": "Balance fetched successfully",
  "result": {
    "username": "James Milligan",
    "balances": {
      "br": 19.8,
      "ph": 0
    }
  }
}

GET /balance/{region}

Get Smile account balance for a specific region.

Path Parameters

Parameter	Type	Required	Description
`region`	string	Required	Region code: `br` (Brazil) or `ph` (Philippines)

Example Request

HTTP

GET /api/balance/br

Example Response

JSON

{
  "success": true,
  "message": "Balance fetched successfully",
  "result": {
    "username": "James Milligan",
    "region": "br",
    "balance": 19.8,
    "coupons": 0
  }
}

Note

Balance endpoints require valid Smile.one cookies to be configured in the system. If cookies are expired, you'll receive an error response.

Products Endpoint

GET /products

Get all available Mobile Legends diamond packages.

Query Parameters

Parameter	Type	Required	Description
`region_slug`	string	Optional	Region code: `br` (Brazil) or `ph` (Philippines)

Example Request

HTTP

GET /api/products?region_slug=ph

Example Response

JSON

{
  "success": true,
  "message": "Product List",
  "result": [
    {
      "id": 1,
      "name": "86 Diamonds",
      "smile_product_id": "mlbb86",
      "slug": "mobilelegends",
      "region_slug": "ph"
    }
  ]
}

Check Role Endpoint

Verify user account before making a purchase. Always call this first to validate the game ID.

GET /check-role

Verify Mobile Legends user ID and zone ID.

Query Parameters

Parameter	Type	Required	Description
`game_id`	string	Required	User's game ID (max 225 characters)
`zone_id`	string	Required	User's zone/server ID (max 225 characters)

Example Request

HTTP

GET /api/check-role?game_id=123456789&zone_id=2345

Example Response

JSON

{
  "success": true,
  "message": "Check Role",
  "result": {
    "username": "PlayerName",
    "game_id": "123456789",
    "zone_id": "2345"
  }
}

Purchase Endpoint

Important

Always call the check-role endpoint first to validate the user's game ID before making a purchase.

POST /purchase

Process a Mobile Legends diamond purchase.

Request Body (JSON)

Parameter	Type	Required	Description
`game_id`	string	Required	User's game ID
`zone_id`	string	Required	User's zone/server ID
`smile_product_id`	string	Required	Product ID from the products endpoint

Example Request

HTTP

POST /api/purchase
Content-Type: application/json

{
  "game_id": "123456789",
  "zone_id": "2345",
  "smile_product_id": "mlbb86"
}

Responses

HTTP 200 OK

{
  "success": true,
  "message": "Purchase Success",
  "result": null
}

HTTP 404 - Product Not Found

{
  "success": false,
  "message": "Product not found"
}

HTTP 500 - Payment Failed

{
  "success": false,
  "message": "Something went wrong, Payment failed"
}

Response Format

All API responses follow this standard format:

JSON

{
  "success": true | false,
  "message": "Response message",
  "result": { } | [ ] | null
}

Field	Type	Description
`success`	boolean	`true` if request was successful, `false` otherwise
`message`	string	Human-readable message about the result
`result`	object/array/null	Response data (null for operations without return data)

Error Handling

HTTP Status Codes

Code	Description
`200`	Success - Request completed successfully
`400`	Bad Request - Invalid parameters or malformed request
`404`	Not Found - Resource not found (e.g., invalid product ID)
`422`	Validation Error - Missing or invalid required fields
`500`	Server Error - Something went wrong on the server

Validation Error Response

JSON

{
  "success": false,
  "message": "Validation failed",
  "errors": {
    "game_id": ["The game_id field is required."],
    "zone_id": ["The zone_id field is required."]
  }
}