Skip to content
Dashboard

Input Schemas (order_input_schema)

In the DanDanPay Reseller API, fulfillment parameters are not hardcoded. Instead, each offer provides a standardized JSON Schema in the order_input_schema field.

When calling POST /v1/orders, you pass these parameters inside the input field:

{
"offer_id": "01981de8-7cb4-7f54-8672-57eb8ee8b47e",
"input": {
"game_user_key": "1919293471",
"game_server_key": "6956"
}
}

Offer schema:

{
"type": "object",
"required": ["game_user_key", "game_server_key"],
"properties": {
"game_user_key": {
"type": "string",
"description": "Player User ID (numbers before parentheses)"
},
"game_server_key": {
"type": "string",
"description": "Zone/Server ID (4 digits in parentheses)"
}
},
"additionalProperties": false
}

input object when placing an order:

{
"game_user_key": "1919293471",
"game_server_key": "6956"
}

If the submitted input fails to validate against the offer schema (e.g. missing required property, invalid data type, or extraneous field when additionalProperties: false), the API returns HTTP 400 Bad Request or 422 Unprocessable Entity:

HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json
{
"code": "INVALID_ORDER_INPUT",
"message": "Validation failed: 'game_server_key' is required"
}

Always fetch fresh offer metadata before rendering the customer payment/checkout form.