Skip to content

Developers

A governed interface to construction cost control

Use stable contracts instead of private database coupling. The checked-in foundation is not a production webhook service: receiver-secret handoff, DNS/IP egress enforcement, key issuance, endpoint and delivery certification remain required.

Scoped credentials

Keys are restricted to an organisation and declared permissions; service credentials never enter browser bundles.

Idempotent operations

Stable request and external IDs support safe retries for currently permitted operations. Financial mutation commands remain closed until separately governed and certified.

Webhook delivery design

The dispatcher models signatures, stable event IDs, retry and status history. One-time receiver-secret provisioning and redirect-safe DNS/IP egress controls are not implemented, so delivery must stay disabled.

Versioned contracts

Responses use explicit definitions and states. Exact monetary transport remains a production-certification requirement; current API consumers must not assume decimal-string money.

Release gate

Do not treat foundation as production certification

Before a live integration, implement receiver-secret handoff and redirect-safe DNS/IP egress policy, then confirm the deployed endpoint, scopes, key rotation, signature verification, retries, redaction and two-tenant isolation in that environment.