API Development And
Integration Guide
Get Started
Overview
Sandbox vs Production
Authentication (API Keys)
Headers & Environments
Product API
Fetch Product List
Product Parameters
Sample Response
Filtering & Pagination
Order API
Place Order (Pull Codes)
Order History (order-list)
View Order Details (order -detail)
Sample Order Payloads
Response Fields Explained
Customer API
Check Account Balance
Credit & Combined Balance
Sample Responses
Common Parameters & Headers
Global Headers
Language Settings
Pagination Standards
Error Handling & Status Codes (Optional)
Common Errors
Status Responses
Retry Logic
Postman Collection & Tools (Optional)
API Testing Guide
Postman Import
Curl Examples
Common Errors
When integrating with WUPEX, it’s crucial to handle common error scenarios correctly. A well-structured approach ensures a reliable user experience and simplifies troubleshooting.
Error Response Structure
All error responses follow this JSON pattern:
json
{
"status": false,
"error": {
"code": "ERROR_CODE",
"message": "Descriptive message to help fix the issue"
}
}
- status: Always false on failure
- error.code: A concise machine-readable identifier
- error.message: A clear, actionable explanation (no sensitive data)
Most Common Error Types
4xx Client Errors
- 400 Bad Request – Malformed request (e.g., missing required fields)
- 401 Unauthorized – Missing or invalid API key
- 403 Forbidden – No permission to access endpoint
- 404 Not Found – Requested resource (e.g., SKU, order) doesn’t exist
- 408 Request Timeout – No response received in time
- 409 Conflict – Conflicting request state or duplicate resource
- 413 Payload Too Large – Request body exceeds allowed size
- 422 Unprocessable Entity – Request is syntactically correct, but semantically invalid (e.g., quantity = 0)
5xx Server Errors
- 500 Internal Server Error – Unexpected server-side failure
- 502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout – API backend issues or maintenance
Handling & Best Practices
- 1. Map HTTP Status to Error Object
- Use the status code and error.code to branch logic in your app—for retries, user messages, or support escalation.
- 2. Use Clear Error Messages
- Messages should clearly explain the problem and how to fix it (e.g., “Invalid SKU: XYZ not found”)
- 3. Avoid Leaking Sensitive Info
- Never expose internal stack traces or environment details in error messages
- 4. Retry Strategy
- Use exponential backoff for transient errors (429, 503, 500) and avoid retries for 400–403 errors
- 5. Centralize Error Logging
- Capture error.code, error.message, timestamp, and any request identifiers for debugging and monitoring
Example Handling Scenarios
|
Scenario
|
HTTP Code
|
Error Code
|
Suggested Handling
|
|---|---|---|---|
|
Invalid/malformed request
|
400
|
INVALID_PAYLOAD
|
Show user-friendly validation error
|
|
Missing or invalid API key
|
401
|
UNAUTHORIZED
|
Request correct API key and retry
|
|
Insufficient permissions
|
403
|
FORBIDDEN
|
Review entitlement or permissions
|
|
Resource not found
|
404
|
NOT_FOUND
|
Handle as "no data", don’t retry
|
|
Rate limit exceeded
|
429
|
TOO_MANY_REQUESTS
|
Pause and retry after backoff
|
|
Temporary server issue
|
503
|
SERVICE_UNAVAILABLE
|
Retry with exponential backoff
|
|
Unexpected server error
|
500
|
INTERNAL_ERROR
|
Alert support team, retry may help
|
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.