Support
Thank you for helping us improve the Wex Health developer experience! This document outlines the process for reporting issues across our SDK ecosystem (Java, Python, JavaScript/TypeScript, and .NET).
How to Report an Issue
Since our SDK source repositories are hosted privately, we provide a centralized triage process via our Developer Portal.
Provide a “Minimum Reproducible Example”
Developers hate vague reports like "It doesn't work." To help us resolve your issue quickly, please provide:
- Your Environment: Language version (Node version, Python version, and so on), OS, and SDK version.
- The Exact Error Message: The full stack trace or the specific error returned by the SDK.
- A Small Code Snippet: A minimal, self-contained piece of code that triggers the bug.
Bug Report Template
Please copy and fill out this template when submitting your report:
SDK Type: [for example, Java, Python, JS, .NET]
SDK Version: [for example, 0.1.0a1]
Environment Details: Runtime: [for example, Node.js 20.x, Python 3.11, JDK 17]
OS: [for example, Windows 11, macOS, Linux]
Issue Description: [A brief description of the bug.]
Exact Error Message:
[Paste full error/stack trace here] Minimum Reproducible Snippet:
// Paste the small code snippet/descriptive steps that triggers the bug here Feature Requests
We welcome suggestions for improvements. When submitting a feature request, please include:
- Motivation: Why is this feature needed?
- Proposed Usage: A short example of how you'd like the new API to look.
Security Disclosures
If you have identified a security vulnerability, please do not report it via the standard support form. Instead, email: gl-sdk-support@wexinc.com .
Contact
For general developer support and SDK inquiries: gl-sdk-support@wexinc.com
Need | Contact |
API credentials & onboarding | Contact the API team you are integrating with |
Bug reports / feature requests | See |
General developer support and SDK inquiries | |
API endpoint reference | See /docs folder for per-endpoint documentation |
Model reference | ClaimDTO, ReceiptDTO, and others documented in /docs |
On this page
- Support