API
A REST API for series, values and computed adjustments. Call it from procurement, ERP or accounts payable so the adjusted price lands where the work already happens.
The Escalake REST API exposes the same objects the interface uses: index series, observations, price adjustment models, and computed adjustments for any period. Filter observations by version, preliminary, final, or revised, or ask for the value as it stood on a given date, and the response states which version it returned. Confirmation state from the sign-off step is included on the adjustment response. Call it from procurement, an ERP, or accounts payable so the adjusted price lands where the work already happens, reading from the same versioned data layer as the app.
curl https://api.escalake.com/v1/pams/steel-frame-2024/adjustment?version=FINAL \
-H "Authorization: Bearer $ESCALAKE_KEY"
{
"period": "2024-Q3",
"adjustmentPct": 4.71,
"cumulativeAdjustmentPct": 11.38,
"dataVersion": "FINAL",
"formulaVersion": 3,
"confirmed": { "buyer": "2024-10-14", "supplier": "2024-10-15" },
"components": [
{ "series": "PPI: Steel Mill Products", "weight": 0.55, "change": 6.9 },
{ "series": "ECI: Manufacturing", "weight": 0.30, "change": 3.1 }
]
}The same objects the interface uses. List and fetch index series, pull observations for a range, list price adjustment models, and get the computed adjustment for any period.
v1 resources
Filter observations by PRELIMINARY, FINAL or REVISED. Ask for the value as it stood on a given date. The response states which version it returned, so downstream systems record the same thing Escalake did.
GET /v1/series/PPI-WPU101/values?version=FINAL
Details
Keys are scoped per tenant and stored encrypted. Rotate without downtime.
Cursor pagination on list endpoints, with published rate limits per plan.
Event delivery on confirmation and data refresh is on the roadmap.
List and fetch index series, pull observations for a date range, list price adjustment models, and get the computed adjustment for any period. These are the same objects the web interface uses, returned as JSON over REST v1.
Requests use a bearer key in the Authorization header. Keys are scoped per tenant and stored encrypted, and you can rotate a key without downtime by issuing a new one before retiring the old.
Yes. Filter observations by PRELIMINARY, FINAL, or REVISED, or request the value as of a specific date. Every response states the version it returned, so a downstream system records the same figure Escalake used.
List endpoints use cursor pagination, and each plan has a published rate limit. The adjustment endpoints return the full component breakdown, cumulative adjustment, and confirmation dates in a single response.
Automate the mechanism, not the judgement.
Explore
We use cookies to run Escalake and to understand site traffic. Choose Accept Minimum for essential cookies plus anonymous visit counting only, or Accept All to also let us link activity to your account. Read our Cookie Policy and Privacy Policy.