Developer reference
API access status
The current boundary between account API-key controls, documented partner integrations and Aiviance internal routes.
Open
Aiviance does not currently publish a general-purpose public API reference. This page records that boundary so internal product routes are not mistaken for supported external contracts.
API keys are controlled credentials
The signed-in product can issue, list and revoke API keys for an account where that capability is enabled. A secret is shown only when issued; stored keys are hashed, scoped to their owner and auditable. Inactive keys are subject to automatic revocation after 90 days.
Possessing an API key does not make every Aiviance route public. A key is usable only with a surface that Aiviance has explicitly documented for that account or partner.
Internal routes are not a reference
The /api/v1 routes used by Aiviance web, mobile, advisor and operational services are application adapters. Unless a route appears in an approved developer contract, its path, request body and response shape may change with the product.
Do not build an integration by discovering or copying browser requests. Internal cron routes, callbacks, webhooks and administration routes are also outside the general public surface.
What a published contract must include
A supported external API will document its base URL, authentication, scopes, entity ownership rules, version, rate limits, errors, idempotency requirements and deprecation policy. If those details have not been supplied for a surface, treat it as unavailable for external use.
To request a supported integration, contact Aiviance with the use case, data scope, expected volume and security model. Also read the developer platform boundary and integration lifecycle.