API Development And
Integration Guide
Get Started
Product API
Order API
Customer API
Common Parameters & Headers
Error Handling & Status Codes (Optional)
Postman Collection & Tools (Optional)
Status Responses
Use this endpoint to retrieve a paginated history of all past orders. It supports searching, sorting, and filtering to help you build order-tracking dashboards, audit logs, or admin tools.
Success Responses (2xx)
- 200 OK
- Indicates the request was successfully processed and returned expected data. Always accompanied by a full response payload (e.g., product list, order details) .
- 201 Created
- Used when a new resource is created on the server, such as an order placement (pull-codes). The response includes resource identifiers and related data .
Informational & Redirection (1xx / 3xx)
- Not used in the current WUPEX JSON API. All interactions return immediate 2xx, 4xx, or 5xx codes without redirection or interim informational codes.
Informational & Redirection (1xx / 3xx)
|
Code
|
Description
|
|---|---|
|
400
|
Bad Request – Malformed request or missing required fields ($error
|
|
401
|
Unauthorized – Missing or invalid x-api-key. User must re-authenticate
|
|
403
|
Forbidden – Valid key, but insufficient permissions for this action
|
|
404
|
Not Found – Resource doesn’t exist (e.g., productCode, orderName)
|
|
409
|
Conflict – Duplicate resource or conflicting request state
|
|
422
|
Unprocessable Entity – Semantic validation failed (e.g., quantity=0)
|
|
429
|
Too Many Requests – Rate limit exceeded; implement retry logic
|
|
413+
|
Payload too large, unsupported media type, etc.
|
Server Errors (5xx)
- 500 Internal Server Error – Generic server error; retry may succeed.
- 502/503/504 – Gateway or service unavailable; indicates backend issues or maintenance
Response Structure
- All responses follow this consistent JSON structure:
- Success Example (200):
json
{
"status": true,
"data": { ... } // varies by endpoint
}
- Error Example (4xx/5xx):
json
{
"status": false,
"error": {
"code": "ERROR_CODE",
"message": "Detailed but safe error description"
}
}
- This schema ensures predictable parsing and handling across your client or server-side code.
Retry Strategies and Logic
- Retry on transient errors (429, 500, 503, 504) using exponential backoff with jitter.
- Do not retry on 400, 401, 403, or 422—these require corrective action before retrying.
- Inspect both HTTP status and error.code when /bresolving issues:<>
- Example: For 400, extract invalid field from error.message to display validation errors to users.
- Example: For 403, prompt user to update permissions or contact support.
Let’s Boost Your
Business Efficiency
Say goodbye to delays, fraud, and complex setups—our solution is built for speed and trust.
Get Latest News for Free!
Sign up to get product updates, new partner alerts, and
exclusive API insights
exclusive API insights
No spam. Unsubscribe anytime
Why WUPEX?
Partners
- Apple
- PSN
- Razer Gold
- Xbox
- PUBG
- Steam
- Jawaker
- Roblox
- Fornite
- Minecraft
- Yalla Ludo
- FC Mobile
- Freefire
Industries
- Banks & Fintech
- Retail & eCommerce
- Payment Gateways
- Telecom & Wallets
- Gaming & Esports
- Corporate Gifting
Resources
- Blog
- FAQ
Company
- About Us
- Meet Our Team
- Contact Us
- Partnership
- Terms & Conditions
Downloads
- Catalogue
- Company Profile
- API Documentation
Features
- Seamless Integration
- Secured API
- Real-Time Delivery
- Bulk Digital Gift Cards
- Fraud Prevention
- Global Brand Access
Support
- Get Started
- Customer Support
- Portal Guide
- API Integration Guide
- Help Center
Copyright © 2024 WUPEX | All Rights Reserved.
Why WUPEX?
Partners
- Apple
- PSN
- Razer Gold
- Xbox
- PUBG
- Steam
- Jawaker
- Roblox
- Fornite
- Minecraft
- Yalla Ludo
- FC Mobile
- Freefire
Industries
- Banks & Fintech
- Retail & eCommerce
- Payment Gateways
- Telecom & Wallets
- Gaming & Esports
- Corporate Gifting
Features
- Seamless Integration
- Secured API
- Real-Time Delivery
- Bulk Digital Gift Cards
- Fraud Prevention
- Global Brand Access
Support
- Get Started
- Customer Support
- Portal Guide
- API Integration Guide
- Help Center
Company
- About Us
- Meet Our Team
- Contact Us
- Partnership
- Terms & Conditions
Resources
- Blog
- FAQ
Downloads
- Catalogue
- Company Profile
- API Documentation
Copyright © 2024 WUPEX | All Rights Reserved.