Document multipart model handling for image edits#896
Conversation
There was a problem hiding this comment.
Pull request overview
Adds Azure OpenAI image editing guidance to the Azure OpenAI integration docs, focusing on multipart (multipart/form-data) behavior and the requirement to pass the Azure deployment/model name directly in the multipart model field (without provider-prefixed aliases).
Changes:
- Documented Azure OpenAI image editing usage and constraints for multipart requests.
- Added an example showing the correct
modelvalue and a counterexample with a provider-prefixed alias. - Added a note explaining why Portkey does not rewrite model aliases inside multipart payloads.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
| </Tabs> | ||
|
|
||
| <Note> | ||
| For Image Edit requests, provider-prefixed model aliases inside multipart payloads are not supported. The `model` value should match the model or deployment name expected by the upstream provider. |
There was a problem hiding this comment.
For image edit you can give add a section and example, then below just put note @provider/modelname in request body is not supported.
| --- | ||
|
|
||
| <Note> | ||
| Image edit requests use `multipart/form-data` and the provider-prefixed model aliases inside multipart payloads is not supported, so pass the upstream provider's model or deployment name directly in the `model` form field instead of values like `@provider/model-name`. |
Summary
/v1/images/editsmultipart requests.modelfield.Test plan