--- title: "Changes to Image to SVG" method: POST path: "/v1/svgs/vectorizations" --- # Changes to Image to SVG `POST /v1/svgs/vectorizations` > Every recorded change to this operation, newest first. ## Timeline Changed in 10 of 28 revisions. - **2026-10-25** `7733c6a9d212`: 1 breaking, 1 info - **2026-10-12** `0391908cbca2`: 1 warning - **2026-09-30** `b2283e5339fe`: 14 warning, 5 info - **2026-09-25** `4d02d06a13b8`: 2 info - **2026-09-17** `9e96cde14a99`: 1 breaking, 13 info - **2026-09-09** `c5063598db50`: 1 breaking, 5 info - **2026-09-07** `a2654af3b241`: 1 info - **2026-09-03** `bca7df4aa12f`: 1 breaking, 13 info - **2026-08-22** `69b0cabf8827`: 1 breaking, 48 warning, 1 info - **2026-07-13** `bb992d04f546`: 1 breaking, 12 warning, 1 info ## Changes - **2026-10-25** `7733c6a9d212`: 1 breaking, 1 info - added `subschema #2, subschema #3, subschema #4, subschema #5` to the response body `oneOf` list for the response status `200` (media type: text/event-stream) - removed `subschema #2, subschema #3, subschema #4, subschema #5` from the response body `oneOf` list for the response status `200` (media type: text/event-stream) - **2026-10-12** `0391908cbca2`: 1 warning - the `top_p` request property's exclusiveMinimum was set to `0.00` - **2026-09-30** `b2283e5339fe`: 14 warning, 5 info - the optional response header `x-quiver-zero-data-retention` removed for the status `200` - the optional response header `x-quiver-zero-data-retention` removed for the status `400` - the optional response header `x-quiver-zero-data-retention` removed for the status `401` - the optional response header `x-quiver-zero-data-retention` removed for the status `402` - the optional response header `x-quiver-zero-data-retention` removed for the status `403` - the optional response header `x-quiver-zero-data-retention` removed for the status `404` - the optional response header `x-quiver-zero-data-retention` removed for the status `408` - the optional response header `x-quiver-zero-data-retention` removed for the status `413` - the optional response header `x-quiver-zero-data-retention` removed for the status `415` - the optional response header `x-quiver-zero-data-retention` removed for the status `429` - the optional response header `x-quiver-zero-data-retention` removed for the status `500` - the optional response header `x-quiver-zero-data-retention` removed for the status `502` - the optional response header `x-quiver-zero-data-retention` removed for the status `503` - the optional response header `x-quiver-zero-data-retention` removed for the status `504` - the request property `temperature` became nullable - the request property `top_p` became nullable - the `presence_penalty` request property default value `0` was removed - the `temperature` request property default value `1` was removed - the `top_p` request property default value `1` was removed - **2026-09-25** `4d02d06a13b8`: 2 info - added `subschema #3` to the `image` request property `anyOf` list - added the non-success response with the status `415` - **2026-09-17** `9e96cde14a99`: 1 breaking, 13 info - added `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5` to the response body `oneOf` list for the response status `200` - removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5` from the response body `oneOf` list for the response status `200` - added the optional property `param` to the response with the `400` status - added the optional property `param` to the response with the `401` status - added the optional property `param` to the response with the `402` status - added the optional property `param` to the response with the `403` status - added the optional property `param` to the response with the `404` status - added the optional property `param` to the response with the `408` status - added the optional property `param` to the response with the `413` status - added the optional property `param` to the response with the `429` status - added the optional property `param` to the response with the `500` status - added the optional property `param` to the response with the `502` status - added the optional property `param` to the response with the `503` status - added the optional property `param` to the response with the `504` status - **2026-09-09** `c5063598db50`: 1 breaking, 5 info - added `subschema #2, subschema #3, subschema #4, subschema #5` to the response body `oneOf` list for the response status `200` (media type: text/event-stream) - removed `subschema #2, subschema #3, subschema #4, subschema #5` from the response body `oneOf` list for the response status `200` (media type: text/event-stream) - response property `usage` reactivated (media type: application/json) - response property `usage/input_tokens` reactivated (media type: application/json) - response property `usage/output_tokens` reactivated (media type: application/json) - response property `usage/total_tokens` reactivated (media type: application/json) - **2026-09-07** `a2654af3b241`: 1 info - added the new optional request property `reasoning_effort` - **2026-09-03** `bca7df4aa12f`: 1 breaking, 13 info - added `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5` to the response body `oneOf` list for the response status `200` - removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5` from the response body `oneOf` list for the response status `200` - added the optional property `retry_after` to the response with the `400` status - added the optional property `retry_after` to the response with the `401` status - added the optional property `retry_after` to the response with the `402` status - added the optional property `retry_after` to the response with the `403` status - added the optional property `retry_after` to the response with the `404` status - added the optional property `retry_after` to the response with the `408` status - added the optional property `retry_after` to the response with the `413` status - added the optional property `retry_after` to the response with the `429` status - added the optional property `retry_after` to the response with the `500` status - added the optional property `retry_after` to the response with the `502` status - added the optional property `retry_after` to the response with the `503` status - added the optional property `retry_after` to the response with the `504` status - **2026-08-22** `69b0cabf8827`: 1 breaking, 48 warning, 1 info - added `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5` to the response body `oneOf` list for the response status `200` - added the new `funding_payment_action_required` enum value to the `code` response property for the response status `400` - added the new `funding_payment_action_required` enum value to the `code` response property for the response status `401` - added the new `funding_payment_action_required` enum value to the `code` response property for the response status `402` - added the new `funding_payment_action_required` enum value to the `code` response property for the response status `403` - added the new `funding_payment_action_required` enum value to the `code` response property for the response status `404` - added the new `funding_payment_action_required` enum value to the `code` response property for the response status `408` - added the new `funding_payment_action_required` enum value to the `code` response property for the response status `413` - added the new `funding_payment_action_required` enum value to the `code` response property for the response status `429` - added the new `funding_payment_action_required` enum value to the `code` response property for the response status `500` - added the new `funding_payment_action_required` enum value to the `code` response property for the response status `502` - added the new `funding_payment_action_required` enum value to the `code` response property for the response status `503` - added the new `funding_payment_action_required` enum value to the `code` response property for the response status `504` - added the new `funding_payment_failed` enum value to the `code` response property for the response status `400` - added the new `funding_payment_failed` enum value to the `code` response property for the response status `401` - added the new `funding_payment_failed` enum value to the `code` response property for the response status `402` - added the new `funding_payment_failed` enum value to the `code` response property for the response status `403` - added the new `funding_payment_failed` enum value to the `code` response property for the response status `404` - added the new `funding_payment_failed` enum value to the `code` response property for the response status `408` - added the new `funding_payment_failed` enum value to the `code` response property for the response status `413` - added the new `funding_payment_failed` enum value to the `code` response property for the response status `429` - added the new `funding_payment_failed` enum value to the `code` response property for the response status `500` - added the new `funding_payment_failed` enum value to the `code` response property for the response status `502` - added the new `funding_payment_failed` enum value to the `code` response property for the response status `503` - added the new `funding_payment_failed` enum value to the `code` response property for the response status `504` - added the new `funding_payment_method_required` enum value to the `code` response property for the response status `400` - added the new `funding_payment_method_required` enum value to the `code` response property for the response status `401` - added the new `funding_payment_method_required` enum value to the `code` response property for the response status `402` - added the new `funding_payment_method_required` enum value to the `code` response property for the response status `403` - added the new `funding_payment_method_required` enum value to the `code` response property for the response status `404` - added the new `funding_payment_method_required` enum value to the `code` response property for the response status `408` - added the new `funding_payment_method_required` enum value to the `code` response property for the response status `413` - added the new `funding_payment_method_required` enum value to the `code` response property for the response status `429` - added the new `funding_payment_method_required` enum value to the `code` response property for the response status `500` - added the new `funding_payment_method_required` enum value to the `code` response property for the response status `502` - added the new `funding_payment_method_required` enum value to the `code` response property for the response status `503` - added the new `funding_payment_method_required` enum value to the `code` response property for the response status `504` - added the new `funding_pending` enum value to the `code` response property for the response status `400` - added the new `funding_pending` enum value to the `code` response property for the response status `401` - added the new `funding_pending` enum value to the `code` response property for the response status `402` - …10 more - **2026-07-13** `bb992d04f546`: 1 breaking, 12 warning, 1 info - added `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5` to the response body `oneOf` list for the response status `200` - added the new `operation_rate_limit_exceeded` enum value to the `code` response property for the response status `400` - added the new `operation_rate_limit_exceeded` enum value to the `code` response property for the response status `401` - added the new `operation_rate_limit_exceeded` enum value to the `code` response property for the response status `402` - added the new `operation_rate_limit_exceeded` enum value to the `code` response property for the response status `403` - added the new `operation_rate_limit_exceeded` enum value to the `code` response property for the response status `404` - added the new `operation_rate_limit_exceeded` enum value to the `code` response property for the response status `408` - added the new `operation_rate_limit_exceeded` enum value to the `code` response property for the response status `413` - added the new `operation_rate_limit_exceeded` enum value to the `code` response property for the response status `429` - added the new `operation_rate_limit_exceeded` enum value to the `code` response property for the response status `500` - added the new `operation_rate_limit_exceeded` enum value to the `code` response property for the response status `502` - added the new `operation_rate_limit_exceeded` enum value to the `code` response property for the response status `503` - added the new `operation_rate_limit_exceeded` enum value to the `code` response property for the response status `504` - removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5` from the response body `oneOf` list for the response status `200` --- [Operation](https://skmtc.dev/quiver/apis/quiverai-api/docs/v1/svgs/vectorizations/post.md) - [API](https://skmtc.dev/quiver/apis/quiverai-api.md) - [Page](https://skmtc.dev/quiver/apis/quiverai-api/changes/v1/svgs/vectorizations/post)