Product connections
Connect eligible external services through approved product or platform integration boundaries.
Integrations and platform connections
Connect the ecosystem without breaking its boundaries.
Depar products and shared services coordinate through explicit APIs, events, domains and trusted service contracts.
Connection model
Use the right interface for the right responsibility.
Public availability varies by product and contract. The Console never presents an integration as active until the authoritative service exposes it.
Business events
Respond to defined lifecycle events without polling private product databases.
Domains and destinations
Route approved public and operational domains to the correct organization or product context.
Scoped credentials
Use purpose-bound access rather than broad shared secrets across products.
Service contracts
Integrate through deliberate request, response, error and versioning conventions.
Observable activity
Preserve delivery, failure, retry and actor context for important integration operations.
Integration path
From business need to observable connection.
Define
Identify the business record, event and authoritative owner.
Authorize
Choose organization, product and credential scope.
Connect
Use the approved API, event or domain contract.
Observe
Handle validation, delivery, failure and retry deliberately.
Govern
Review access, usage and audit context over time.
Availability is contract-led.
Customer API keys, webhooks and third-party connectors appear only when the responsible service provides a safe, supported customer contract. Contact us to review a specific integration requirement.