Reimbursement Methods
Overview
The Reimbursement Methods API provides a centralized way to manage how funds are returned to consumers (for example, Direct Deposit, Check). These endpoints allow developers to list all available methods for a specific consumer or retrieve the granular details of a single method.
Key Features
- Dynamic Filtering: Search by plan year, primary status, or specific method types (for example, Check vs. ACH).
- Contextual Security: Scopes requests via
consumer_idandemployer_idto ensure data privacy. - Full Resource State: Access comprehensive metadata including account masking and creation timestamps.
Use Cases
- Member Dashboards: Listing all active reimbursement channels for a user.
- Selection Interfaces: Allowing a user to pick a primary payment method for a specific plan year.
- System Verification: Confirming a user’s payment details before processing a claim payout.
Scopes & Permissions
Scope | Description | Required For |
| Read access to reimbursement methods | GET (List & Individual) |
| Create/Update access | POST, PUT, PATCH |
Core Concepts
The Resource Model
A ReimbursementMethod defines the “where” and “how” of a payout. Methods are usually tied to specific Plan Years.
Key Attributes
method_type: The type of reimbursement (for example, DirectDeposit, Check).is_primary: A boolean flag. Only one method can be the primary destination for funds per plan year.- Contextual IDs: Use
employer_idandconsumer_idto ensure you are fetching data for the correct entity.
Pagination
The list endpoint uses standard zero-based pagination.
Parameter | Type | Description |
| Integer | The page number to retrieve (Default: 0). |
| Integer | Items per page (Default: 20, Max: 100). |
Example Response Metadata
"pagination": {
"page": 0,
"page_size": 20,
"total_items": 45,
"total_pages": 3
}
Error Handling
Status Code | Meaning | Common Causes |
| Bad Request | Missing |
| Unauthorized | Token is missing, expired, or lacks |
| Not Found | The |
| Server Error | Internal system failure. |
Idempotency
All endpoints in this section use the GETmethod. They are idempotent and safe, meaning they do not modify server state and can be called repeatedly with the same result.
Endpoints
/v1/reimbursement-methods?consumer_id=consumer_id&plan_year_id=plan_year_id&method_type=me...