Integration model

How Infrenta supports data exchange during commercial implementation — not as a self-serve public API catalog.

Infrenta can exchange project and commercial data with other systems when that work is scoped during implementation.

This is not currently a self-service public API. There is no public endpoint catalog, no self-serve credential signup, and no unrestricted REST surface for every project object on this website. Project and commercial records live in the authenticated application behind company isolation.

Limited access

System-to-system access is reviewed with the customer and provisioned when it is part of the written agreement. Requirements, identifiers, and operational expectations are defined for that implementation.

If you need to connect an ERP, document repository, or owner data room, start with Discuss an integration.

What an integration attaches to

Integrations should hang from the same objects the product uses:

  • company (tenant) boundary
  • project identity
  • issued estimate revisions
  • documents and drawings
  • commitments and selected supplier values, when in scope

Draft rows are not a stable contract. Prefer approved revisions. See Connected project record.

Principles

  • Stay inside the customer’s company. Never assume cross-organization access.
  • Prefer issued revisions over drafts.
  • Do not treat GeoLab scores as sealed design deliverables.
  • Do not cache Trade & Tariff figures as if they were a live customs feed.
  • Do not imply a self-serve purchasing or API-key portal.

Topics

These pages describe integration *concerns*. They do not publish unverified endpoint paths.