API Documentation

This documentation provides details on the available endpoints of the UC Activator API.

Endpoints

1. Activate UC Code

Endpoint: POST /api/activate

Activate a UC code for a player using the provided activation request data.

Request

• Headers:

• X-Api-Key: Your API key.

• Body:

• player_id (int): The Player ID.

• uc_code (str): The UC Code to be activated.
• uc_value (str): The value associated with the provided UC Code.
• midas_email (str): Midasbuy Account's Email (Optional).
• midas_password (str): Midasbuy Account's Password (Optional).

{
  "player_id": 5555555555,
  "uc_code": "AeCmNADi2R2bQbF3A3",
  "uc_value": "60 UC",
  "midas_email": "example@example.com", // Optional (null)
  "midas_password": "example_password" // Optional (null)
}

Response

• 200 OK

{
  "result_code": 0, // Indicates the outcome of the activation (see descriptions below)
  "activation_data": {
    "activation_success": true,
    "activation_id": "482915829538",
    "player_id": "5555555555",
    "nickname": "PlayerNickname", // Optional (null)
    "uc_pack": "60 UC",
    "redeem_code": "AeCmNADi2R2bQbF3A3",
    "details": "Activation details", // Optional (null)
    "redemption_time": "1721955702", // Optional (null)
    "region": "EU", // Optional (null)
  }
}

- 401 Unauthorized

{
  "message": "Missing X-Api-Key header"
}

{
  "message": "Access error"
}

- 403 Forbidden

{
  "message": "Insufficient balance"
}

- 503 Service Unavailable

{
  "message": "API activator is disabled at the moment"
}

- 500 Internal Server Error

{
  "message": "Activation failed"
}

{
  "message": "Detailed error message"
}

Internal Server Error

2. Result Codes

The following result codes indicate the outcomes of the UC Code activation process:

• 0: Activation Successful

  • The UC Code was successfully activated.
  • The activation was successful, and the code has been activated without any issues.

• 101: Code Already Activated by This Player

  • The UC Code was previously activated for the same Player ID.
  • The UC Code has already been used by the Player ID provided in the request data.

• 102: Code Already Activated by Another Player

  • The UC Code was previously activated for a different Player ID.
  • The UC Code has already been used by another player.

• 201: Invalid Code Format

  • The UC Code format is incorrect.
  • The entered UC Code does not match the required format, such as having an incorrect length or containing invalid characters.

• 202: Invalid Player ID

  • The Player ID format is incorrect.
  • The specified Player ID does not exist, is invalid according to the system's requirements, or does not start with the digit: 5.

• 301: Technical Issue

  • There was a technical problem on the server side during the activation process.
  • This issue can also occur rarely if the UC Сode is expired or consists of an invalid set of characters. If the server returns this error, the request cost is not charged.