Compatibility and legacy paths

AI4CALL keeps legacy paths and field names working while integrations migrate to the current API. Deprecated operations are intentionally hidden from the main API Reference.

Use the canonical endpoint and camelCase request fields for new work. In particular, outbound requests accept assistantApiKey, addPrompt, callResultUrl, ipPbx, and sipPort, while their legacy names remain accepted.

Do not remove legacy fields from an existing integration until it has been tested against the current service. When a response contains a public assistantId, use it for new links and user-facing references; never expose assistantApiKey.