Salesforce, Studio, and AI API access

The reference also includes production routes that accept API-key authentication outside the core rendering workflow:

• Salesforce: inspect the configured connection, delivery resources, object types, and object fields. Use production or sandbox for the commercial environment path parameter. Creating or changing the connection requires session authentication.
• Studio: list accessible templates, workflows, and folders through /api/v1/studio/items. The standard listing requires the Studio unified-table feature; a disabled feature returns 404. Specialized UI browsing contexts are outside the standard-list contract.
• AI chats: create a chat for one accessible file_id through POST /api/v1/ai-chats. The configured AI provider must accept the file. file_ids is no longer supported. Question, response, and other chat routes use session authentication, so this route alone is not a complete API-key chat integration.

API-key authentication is only the first check. Account permissions, subscriptions, integration configuration, and feature flags still control availability. These commercial routes do not establish government approval.