REST / JSON
Project, document, quantity, asset and workflow interfaces for server-to-server and application integration.
Developer Preview
Connect built asset evidence to the systems around it.
CivilQuant is designed to expose governed project, quantity, asset and evidence capabilities through integration surfaces. This public page describes the integration model; it does not imply every interface is generally available today.
Integration model
Stable objects, explicit evidence, controlled actions.
Developer interfaces should make it possible to integrate CivilQuant without bypassing tenant boundaries, review state or evidence provenance.
Events & webhooks
Planned event surfaces for revision, review, issue and workflow-state changes.
SDK roadmap
Client libraries can target JavaScript/TypeScript, PHP/Laravel, Python, Java, .NET and other enterprise stacks as interfaces stabilise.
BIM & document integration
Connect model/document sources to governed extraction and measurement workflows.
ERP / finance integration
Map authorised commercial and asset records into wider procurement, finance and asset systems.
Agent-ready tools
Tool-oriented interfaces are a natural future surface, but actions must preserve permissions, evidence and review gates.
Illustrative API shape
Evidence first, not magic strings.
The payload below is a design example, not a claim of a production endpoint.
POST /api/v1/projects/{project}/measurements
{
"source_revision": "A-201-C",
"entity": "W04",
"quantity_type": "volume",
"unit": "m3",
"inputs": {"length": 12.0, "height": 3.0, "thickness": 0.25},
"formula": "length * height * thickness",
"review_state": "draft"
}
→ {
"value": 9.0,
"unit": "m3",
"evidence_status": "linked",
"issue_state": "review_required"
}Availability
Do not build against a marketing page.
Use production developer documentation and credentials supplied to your account or enterprise engagement. Preview examples on this site are architectural illustrations until explicitly marked otherwise.