State volume breakdown across this branch's loans
Ranks the states this branch's loans were secured in, by volume. Labels are two-letter state abbreviations. This is where the branch actually transacted, which is narrower than where it is licensed — licensed states are returned by GET /v1/branches/{nmlsId}.
In: header
Path Parameters
Branch NMLS ID
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/branches/string/breakdowns/states" \ -H "Content-Type: application/json" \ -d '{}'{
"cursor": "string",
"data": [
{
"excluded": 0,
"id": "string",
"label": "string",
"name": "string",
"pctUnits": 0,
"pctVolume": 0,
"units": 0,
"volume": 0
}
],
"total": 0,
"totals": {
"excluded": 0,
"units": 0,
"volume": 0
},
"truncated": true
}{
"error": "string"
}{
"error": "string"
}{
"error": "string"
}{
"error": "string"
}{
"error": "string",
"limit": 0,
"size": 0
}Loan officers who wrote this branch's loans POST
Ranks the loan officers whose loans public record attributes to this branch, by volume. Each label is the LO's NMLS ID, so it chains straight into `GET /v1/originators/{nmlsId}`. This is the branch's RECORDED roster, not its licensing roster: it answers who actually wrote loans here in the period, which is narrower than everyone registered to the branch and can include someone who has since moved. For the licensed managers on file, read `managers` on `GET /v1/branches/{nmlsId}`.
Count branches matching filters POST
Return the exact number of branches matching the given filters. Accepts the same request body as `listBranches` (pagination and sort are ignored). Use this when you only need a total; to get the matching branches themselves, send the same request body to `listBranches`.