JSON API with scoped bearer keys
Read endpoints cover projects, pipeline, defects, invoices, schedules, daily reports, documents, RFIs, change orders, payments and purchasing. Selected schedule, pipeline and defect changes have write endpoints. Keys carry read or write scope, expiry and the issuing user’s permissions; requests are limited to 60 per minute.
Signed webhooks with delivery history
Endpoints subscribe to named event families such as project, schedule, invoice, payment, purchasing, defect, document and customer changes. Deliveries are HMAC-signed, logged and can be tested or retried.
MCP access under the same permissions
A downloadable connection creates a time-limited read-only key for search, fetch and operational overviews. A separately issued write-scoped key can expose only the change actions allowed by the user’s role; company settings decide whether a change executes or waits for review.
File-based exchange where it is actually implemented
The product exports filtered operational lists as CSV, invoices as printable PDF or XRechnung UBL XML, and complete tenant database records as NDJSON. Contact master data can be prepared for import from CSV or XLSX during setup. Each format should be tested against the receiving system.