API Common Result Codes (RstVal)
Standard definitions for RstVal and RstMsg, the common API response fields in the GIIP platform.
📋 Overview
Every GIIP API includes RstVal (integer code) and RstMsg (descriptive message) at the top level of its response data for execution tracking. These values follow the standards defined in the tDefRst (Result Definition) table in the database.
The term tRstVal mentioned by users refers to the drRstVal column within the tDefRst table. Developers can refer to the codes defined below to implement proper error handling when integrating with our APIs.
📡 Major Result Codes
| RstVal | RstMsg | Meaning | Remarks |
|---|---|---|---|
| 200 | Process has done successfully | Success | Standard success response |
| 400 | No data found | Bad Request | Missing parameters or empty data |
| 401 | Unauthorized | Auth Failed | Key error or session expired |
| 403 | Forbidden | No Permission | Insufficient access rights |
| 404 | No data found | Not Found | Resource does not exist |
| 500 | System error | System Error | Server-side or DB error |
🔍 Detailed Result Codes (tDefRst)
The following is a list of detailed result codes used internally by the system, including domain-specific messages for points, signups, and external integrations.
| drRstVal | drRstMsg | Category |
|---|---|---|
| 100 | Starting Stored Procedure... | System |
| 102 | Data is not match | Validation |
| 201 | Created successfully | Creation |
| 204 | No content available | Data |
| 211 | It is clean email. go next... | Signup |
| 212 | Already registered user. | Signup |
| 220 | Charge process has done successfully | Billing/Points |
| 221 | Point process has done successfully | Points |
| 230 | Buying process has done successfully | Purchase |
| 250 | Prayed successfully | Others |
| 300 | Permission error | Permissions |
| 301 | Not enough point | Points |
| 302 | Already data exists. | Duplicate |
| 312 | Pre-registered but not have User data. | Signup Status |
| 313 | Input status is lower than dbStatus. | Integrity |
| 320 | It cannot be processed point processing | Points |
| 330 | You have NFT Token already. | Asset |
| 332 | Already sold out. | Purchase |
| 333 | Event item limit reached. | Event |
| 390 | Already registered this wallet. | Auth/Wallet |
| 405 | Method not allowed | Server/HTTP |
| 409 | Conflict: Resource already exists | State Conflict |
| 410 | Gone: Resource no longer available | Expired/Deleted |
| 420 | You don't have enough point | Points |
| 421 | Not same point and point history. | Integrity |
| 502 | Bad Gateway: Upstream error | Network |
💡 Developer Tips
- Success Check: We recommend proceeding with business logic only when
RstValis200. - Error Handling:
400-series codes indicate the client needs to fix the request, while500-series codes require investigation by system administrators. - Message Usage:
RstMsgis intended for developer debugging. We suggest implementing separate locale-specific messages for end-users.
Troubleshooting
| Symptom | Cause | Resolution |
|---|---|---|
API response returns RstVal 401 | Access Key/Secret Key error or expired session | Re-check your auth keys, refresh the session, and resend the request. |
RstVal is 400 or 404 with empty data | Missing required parameter or the requested resource does not exist | Verify the request parameters and retry with a valid, existing resource identifier. |
Processing stops with RstVal 301/420 | A business condition such as insufficient points is not met | Check RstMsg (e.g., Not enough point), satisfy the prerequisite, then retry. |
RstVal returns 500/502 | Server-side/DB error or an upstream gateway error | Do not retry from the client; contact the system administrator with the RstMsg. |
Related Documents: