curl --request POST \
--url https://www.presolve.com/api/v1/resolutions/{resolutionId}/allocation-previews \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api-key>' \
--data '
{
"amountCents": 50000000000,
"excludeExpenseIds": [
"<string>"
],
"excludeLienIds": [
"<string>"
],
"subtractExisting": true
}
'const options = {
method: 'POST',
headers: {'x-api-key': '<api-key>', 'Content-Type': 'application/json'},
body: JSON.stringify({
amountCents: 50000000000,
excludeExpenseIds: ['<string>'],
excludeLienIds: ['<string>'],
subtractExisting: true
})
};
fetch('https://www.presolve.com/api/v1/resolutions/{resolutionId}/allocation-previews', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://www.presolve.com/api/v1/resolutions/{resolutionId}/allocation-previews"
payload = {
"amountCents": 50000000000,
"excludeExpenseIds": ["<string>"],
"excludeLienIds": ["<string>"],
"subtractExisting": True
}
headers = {
"x-api-key": "<api-key>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"success": true
}{
"success": false,
"error": "<string>",
"code": "<string>"
}{
"success": false,
"error": "<string>",
"code": "<string>"
}{
"success": false,
"error": "<string>",
"code": "<string>"
}{
"success": false,
"error": "<string>",
"code": "<string>"
}{
"success": false,
"error": "<string>",
"code": "<string>"
}{
"success": false,
"error": "<string>",
"code": "<string>"
}Preview the settlement allocation waterfall
Pure computation, no writes: fee → litigation costs → liens → client recovery with referral-fee sub-split.
Supports one selected organization via organizationId. Omit it to use the key’s organization. HQ descendant access requires an active acting attorney with hq:view_child_orgs, cases:view, cases:view_all, hq:view_all_cases, accounting:view, accounting:view_all, hq:view_all_accounting, settlements:view, disbursements:view. Existing key scopes still apply. The selector requires an integration API key; legacy partner/OIDC routing is unchanged. Repeat the selector on every cursor page, related mutation, upload completion, and detail/download request. See HQ authorization.
Requires the funds:read scope. Rate tier: read.
curl --request POST \
--url https://www.presolve.com/api/v1/resolutions/{resolutionId}/allocation-previews \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api-key>' \
--data '
{
"amountCents": 50000000000,
"excludeExpenseIds": [
"<string>"
],
"excludeLienIds": [
"<string>"
],
"subtractExisting": true
}
'const options = {
method: 'POST',
headers: {'x-api-key': '<api-key>', 'Content-Type': 'application/json'},
body: JSON.stringify({
amountCents: 50000000000,
excludeExpenseIds: ['<string>'],
excludeLienIds: ['<string>'],
subtractExisting: true
})
};
fetch('https://www.presolve.com/api/v1/resolutions/{resolutionId}/allocation-previews', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://www.presolve.com/api/v1/resolutions/{resolutionId}/allocation-previews"
payload = {
"amountCents": 50000000000,
"excludeExpenseIds": ["<string>"],
"excludeLienIds": ["<string>"],
"subtractExisting": True
}
headers = {
"x-api-key": "<api-key>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"success": true
}{
"success": false,
"error": "<string>",
"code": "<string>"
}{
"success": false,
"error": "<string>",
"code": "<string>"
}{
"success": false,
"error": "<string>",
"code": "<string>"
}{
"success": false,
"error": "<string>",
"code": "<string>"
}{
"success": false,
"error": "<string>",
"code": "<string>"
}{
"success": false,
"error": "<string>",
"code": "<string>"
}Authorizations
Org-issued integration API key (service account credential). The plaintext secret is shown once at creation.
Path Parameters
Resolution id
Query Parameters
Select one organization for this request. Defaults to the key organization. An HQ key may select an active descendant when its active acting attorney has the required HQ and resource permissions. Repeat the same organizationId on related mutations, upload completion, detail requests, and every cursor page. See /authorization.