跳到主要内容

aiOpenaiImagesGenerations

Map aiOpenaiImagesGenerations(profileId, AiOpenaiImagesGenerationsRequest)

POST /api/2.0/ai/openai/{profileId}/v1/images/generations

OpenAI image generation passthrough

OpenAI-compatible image generation for the document editor's AI plugin, working exactly as the chat-completions passthrough does: the profile named by profileId is resolved server-side, its credentials are attached, and the body reaches the provider unchanged. The provider's status and body are relayed verbatim, so its 429 and its own error envelope surface as they stand. A body larger than this route accepts is refused before it is forwarded. A client disconnect aborts the provider call.

Parameters​

NameInTypeDescriptionNotes
profileIdpathStringThe AI provider profile identifier.[required] [example: 00000000-0000-0000-0000-000000000000]
AiOpenaiImagesGenerationsRequestbodyMapAn OpenAI image-generation request, forwarded to the provider byte for byte. The shape is the provider's, not this API's, and the credentials come from the profile in the path.[required]

Responses​

Status codeDescriptionTypeResponse headers
200The provider's own response, relayed verbatim with its status and content type.Map-
401Missing asc_auth_key cookie or Authorization header.AiErrorResponse-
403AI is disabled for this portal, the caller is a guest, or the room named by entityId is one the caller cannot open. Relayed from the DocSpace AI service or the Files API.aiOpenaiChatCompletions_403_response-
404No profile with this identifier exists for the caller.aiOpenaiChatCompletions_403_response-
413The request body is larger than this route accepts.aiOpenaiChatCompletions_403_response-
429Relayed verbatim from the AI provider, which is rate-limiting this portal's key.aiOpenaiChatCompletions_403_response-
500Unhandled failure. The reason is logged server-side and never echoed back.aiOpenaiChatCompletions_403_response-
502The AI provider could not be reached, or answered with a failure of its own.aiOpenaiChatCompletions_403_response-

Return type​

Map

Authorization​

cookieAuth, bearerAuth

HTTP request headers​

  • Content-Type: application/json
  • Accept: application/json