Users & Identity
Core operations for managing user profiles, identity verification, and account-level preferences. Users & Identity provides the foundation for managing participant records, identity validation, and user-level configurations across WEX platforms. It enables developers to create and maintain user profiles, verify identity and banking details, and manage communication preferences. Use this resource to onboard users, ensure compliance through verification workflows, and maintain accurate, up-to-date identity and account data that supports downstream benefits and financial operations.
Core Identity Services
Identity & Person Management API
This suite serves as the central repository for unified identity data, providing a single view of all individuals within the platform, including Consumers, Dependents, Authorized Signers, and Business Contacts.
-
Unified Identity Resolver: Resolve any unique
person_idinto a name, role type, and business association to facilitate cross-entity routing. -
Family & Delegation Mapping: Establish a “Household View” by anchoring dependents and account delegates to primary consumers.
-
On-Demand Data Expansion: Optimize performance by selectively retrieving secondary data blocks such as addresses, employment records, or protected personal data.
-
Identity Hierarchy: Consumers are anchored to a Business (Employer), while their respective dependents and signers are anchored directly to the Consumer.
Notification Preferences API
Manage how and why consumers receive communications through a comprehensive two-tier preference model.
-
Internal Triggers: Manage core event triggers—such as enrollment success or claim denials—that determine if an alert is generated.
-
External Delivery: Control the delivery channels—Email, SMS, or Push—used to send generated alerts to the consumer.
-
Hierarchy of Choice: The system follows a gatekeeping flow, checking if a trigger is enabled internally before validating if the external delivery channel and category opt-ins are active.
-
Master Switches: Utilize global toggles to enable or disable entire communication mediums across the platform.
Organizational Foundations
Administrators API
The foundational step in setting up a new domain by establishing the root business entity.
-
Hierarchical Anchor: Represents TPAs or large corporate entities that oversee all downstream employers and plans.
-
Safe Provisioning: Mandatory idempotency ensures that only one Administrator entity is created per unique key during onboarding.
Business Management API
Manages the operational tiers of the hierarchy, including Employers, Divisions, and Departments.
-
Multi-Tenant Hierarchy: Supports deeply nested parent-child relationships for complex corporate structures.
-
Lineage Awareness: Specialized tools to “walk” up the organizational tree from child nodes to the root Administrator.
Integration Standards
Security & Privacy Controls
Managing sensitive data requires rigorous compliance and visibility settings:
| Mode | Format Example | Access Level |
| MASKED | xxx-xx-1234 | Default for standard users. |
| LAST4 | 1234 | For verification and support workflows. |
| UNMASKED | 555441234 | Restricted to high-level admin and tax operations. |
Scopes & Permissions
| Scope | Description | Required For |
| read:person | View unified identity and demographic data. | All GET operations. |
| read:notifications | Access consumer communication settings. | GET operations. |
| write:notifications | Modify internal and external preferences. | PUT operations. |
| admin:domain | Manage top-level domain entities. | Administrator creation (POST). |
| write:business | Create or modify business entities. | POST/PATCH operations. |
Global Error Reference
| Status Code | Meaning | Common Causes |
| 400 | Invalid Request | Missing required IDs, malformed UUIDs, or invalid data formats. |
| 403 | Forbidden | Insufficient permissions for unmasked data or unauthorized domains. |
| 404 | Not Found | No person, consumer, or business record matches the provided UUID. |
| 405 | Not Enabled | The specific feature module is not active for the requester's domain. |
| 409 | Conflict | Duplicate Idempotency-Key or business EIN already exists. |
Endpoints
v2/external-notification-preferences?person_id=person_id
v2/external-notification-preferences?person_id=person_id
v2/notification-preferences?person_id=person_id
v2/notification-preferences?person_id=person_id
/v1/authorized-signers?consumer_id=&expand=&ssn_mode=MASKED
/v1/consumers/{consumer_id}?expand=&ssn_mode=MASKED
/v1/dependents?consumer_id=&expand=&ssn_mode=MASKED
/v1/persons/{person_id}