# Aiviance developer platform boundary What is available to integration partners today, and what remains an internal product interface. This reference distinguishes supported integration surfaces from internal implementation details. It does not promise public access to Aiviance's internal APIs. ## Supported surfaces Published connectors, file import formats and explicitly documented partner workflows are supported surfaces. Each surface states its authentication, data scope and lifecycle. ## Internal interfaces Routes used by Aiviance applications, including internal `/api/v1` endpoints, are not public contracts unless a developer reference explicitly says otherwise. They may change without partner notice. ## Versioning promise When a public API is released, its documentation will define versioning, deprecation windows, scopes, rate limits and error formats. Until then, integrations require a documented partner agreement. ## Request access Contact Aiviance with the use case, required data, expected volume and security model. We assess the smallest safe integration surface rather than exposing broad account access.