Orders
Create Order
Submit a service order with the service code and required data.
Modified at May 2, 2026, 02:35 PM UTC
POST/api/orderorder.create
Use this request to submit work to a selected service.
The data object must match the selected service input schema. Call Service Detail to read the current payload schema, price, and item limits before submitting an order.
Request
curl "https://cekceir.online/api/order" \
-X POST \
-H "Authorization: Bearer <api_key>" \
-H "Content-Type: application/json" \
-d '{
"code": "example",
"data": "example"
}'Request Fields
| Field | Type | Required | Description |
|---|---|---|---|
| Authorization | header string | Yes | Bearer token header in the format Bearer <api_key>. |
| code | string | Yes | Service code. |
| data | object | Yes | Payload accepted by the selected service. |
Success Response
{ "status": "success", "reference_id": "provider-reference-123", "message": "Pesanan-mu telah berhasil kami proses.", "processed": 1, "processed_success": 1, "processed_error": 0, "remaining_balance": 98500, "result": { "status": "registered" }, "error_message": null, "order_id": 321, "transaction_id": 654, "service_code": "cek_imei", "total": 1, "price": 1500, "total_price": 1500, "charged_amount": 1500, "refunded_amount": 0, "balance_before": 100000, "created_at": "2026-04-26T00:00:00.000Z"}Service Examples
The service references map each service code to its request payload and response shape. Monetary fields such as price, total_price, and remaining_balance are resolved from the authenticated account, access channel, and active service rule.
Response Fields
| Field | Type | Required | Description |
|---|---|---|---|
| status | string | Yes | Order result, such as pending, success, partial, or failed. |
| reference_id | string or null | No | Provider reference when available. |
| message | string | Yes | Human-readable result message. |
| processed | number | Yes | Number of submitted items processed. |
| processed_success | number | Yes | Number of items that succeeded. |
| processed_error | number | Yes | Number of items that failed. |
| remaining_balance | number | Yes | Available balance after the order. |
| result | object or null | No | Service result payload when available. |
| error_message | string or null | No | Error message when the order failed or partially failed. |
| order_id | number | Yes | Order ID. |
| transaction_id | number | Yes | Wallet transaction ID created for the order. |
| service_code | string | Yes | Service code used by the order. |
| total | number | Yes | Number of order items. |
| price | number | Yes | Unit price. |
| total_price | number | Yes | Total order price before capture or refund adjustment. |
| charged_amount | number | Yes | Amount captured from the wallet. |
| refunded_amount | number | Yes | Amount refunded to the wallet. |
| balance_before | number | Yes | Available balance before the order. |
| created_at | ISO datetime | Yes | Order creation time. |
HTTP Status
| Create result | HTTP status | Description |
|---|---|---|
| pending | 201 | The order was accepted and is waiting for completion. |
| success | 200 | All submitted items succeeded. |
| partial | 207 | Some submitted items succeeded and some failed. |
| failed | 503 | The order failed. |
Validation Error
If data does not match the selected service schema, the API returns 422 ORDER_VALIDATION_ERROR:
{ "error": true, "code": "ORDER_VALIDATION_ERROR", "message": "Format order mu tidak sesuai dengan format layanan yang kamu minta.", "source": "order", "errors": { "data": ["/imeis: must NOT have fewer than 1 items"] }, "traceId": "01234567-89ab-cdef-0123-456789abcdef"}