This object allows for the management of many cases across a number of borrowers. That is to say that a supercase can create, manage, and close many cases at once.
This is particularly useful if an issue occurs which affects a large group of borrowers.
- Cases created by a supercase are called
subcases - A supercase can only manage cases it has created (i.e., NOT cases created via the
/casesendpoint)
Managing "who" is affected by a supercase is an important aspect of supercases:
- A
memberof a supercase is one "borrower-loan" pairing. - A
populationis a set of members added at once.- A supercase might have many populations if different members are added at different times.
- It's useful to keep track of sets of members like this because different actions might need to be taken on different members depending on when they're added to a supercase.
- A
population's membership may be changed until it is "committed" by settingisDraft: false, at which time the memberships are locked and subcases are created.
Security
oauth2(Required scopes: supercase:list) or bearerAuth or apiKeyHeader
GET
- oauth2
- bearerAuth
- apiKeyHeader
curl -i -X GET \
'https://sandboxapi.peach.finance/api/supercases?limit=25&startingAfter=string&endingBefore=string&offset=0&sortBy=-id&supercaseType=generic&femaDisasterNumber=0&status=initiated' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Success
Response
{ "count": 0, "nextUrl": "string", "previousUrl": "string", "status": 0, "total": 0, "data": [ { … } ] }