# Image Edits API not returning Rate Limit headers **URL:** \ **Category:** Bugs\ **Tags:** api\ **Created:** [July 18, 2025, 11:36am UTC](https://community.openai.com/t/image-edits-api-not-returning-rate-limit-headers/1318889 "2025-07-18T11:36:11Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Jibbed](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/jibbed/32/655861_2.png) [@Jibbed](https://community.openai.com/u/Jibbed)\ **Post date:** [July 18, 2025, 11:36am UTC](https://community.openai.com/t/image-edits-api-not-returning-rate-limit-headers/1318889/1 "2025-07-18T11:36:11Z")
I don’t see rate limit headers in response to requests to the image /edits endpoint - [`https://api.openai.com/v1/images/edits`](https://api.openai.com/v1/images/edits) This is what the [docs](https://platform.openai.com/docs/guides/rate-limits) state: [![r/ChatGPT - Image Edits API not returning Rate Limit headers|750xauto](https://us1.discourse-cdn.com/openai1/original/4X/1/e/e/1ee0c05e1108a59dbce763a0aaf04ade30531774.png)](https://preview.redd.it/image-edits-api-not-returning-rate-limit-headers-v0-42hrx0vfi4df1.png?width=988&format=png&auto=webp&s=3c46d634ede766b3df242cddc60dee0bb3e3774f) But the headers I get back look like this - is it a bug or am I misunderstanding something? `date: Tue, 15 Jul 2025 22:28:25 GMT` `content-type: application/json` `content-length: 2897135` `openai-version: 2020-10-01` `openai-organization: user-zo0tlghpq74ij3 __________ ` `openai-project: proj_OLGHmRkAG4EeOyC ________ ` `x-request-id: req_f3529274437866a51baa564416828___` `openai-processing-ms: 23646` `strict-transport-security: max-age=31536000; includeSubDomains; preload` `cf-cache-status: DYNAMIC` `set-cookie: __cf_bm=Mw05dyLQHeiVBBLhGkNcbdEvhdQVLEYrdjalbq45b.U-1752618505-1.0.1.1-7euuLrT8AcbHz.PaLx4kkUHvWZ5EKZ.7liJk3VCjqSObbsB_______ KpZuFHFbPkOxGDpnDu1HtGjhBSIjR6wyfJtG1hiqlsc.4; path=/; expires=Tue, 15-Jul-25 22:58:25 GMT;` [`domain=.api.openai.com`](http://domain=.api.openai.com/)`; HttpOnly; Secure` `x-content-type-options: nosniff` `set-cookie: _cfuvid=HYz3PpjA8 ______ zUjOhiJgLZL7rXeiHUsLQfA-1752618505788-0.0.1.1-604800000; path=/;` [`domain=.api.openai.com`](http://domain=.api.openai.com/)`; HttpOnly; Secure; SameSite=None` `server: cloudflare` `cf-ray: 95fcb0c54bafccad-MAN` `alt-svc: h3=":443"; ma=86400` ---
**Author:** ![aprendendo.next](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/aprendendo.next/32/721758_2.png) [@aprendendo.next](https://community.openai.com/u/aprendendo.next)\ **Post date:** [July 18, 2025, 11:49am UTC](https://community.openai.com/t/image-edits-api-not-returning-rate-limit-headers/1318889/3 "2025-07-18T11:49:44Z")
I just confirmed, it seems that the rate limit is indeed missing out from the headers. ---
**Author:** ![\_j](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/_j/32/766292_2.png) [@\_j](https://community.openai.com/u/_j)\ **Post date:** [July 18, 2025, 3:30pm UTC](https://community.openai.com/t/image-edits-api-not-returning-rate-limit-headers/1318889/4 "2025-07-18T15:30:15Z")
The same lack of service header metadata is on the moderations endpoint, where it has more use because of the rate limit much lower than high-tier org AI models that must have inputs preapproved. ---
**Author:** ![Jibbed](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/jibbed/32/655861_2.png) [@Jibbed](https://community.openai.com/u/Jibbed)\ **Post date:** [July 20, 2025, 12:12am UTC](https://community.openai.com/t/image-edits-api-not-returning-rate-limit-headers/1318889/5 "2025-07-20T00:12:40Z")
OpenAI live(ish)chat responded after a couple of days. I can only post 2 links as a new user so hobbled the rest: * * * Thank you for reaching out to OpenAI Support. We understand your concern about the absence of rate limit headers when using the gpt-image-1 endpoint, and we appreciate you checking in, it’s a great question. You’ve reached our human support team. At this time, the absence of standard rate limit headers for the gpt-image-1 endpoint is expected behavior. Unlike text-based endpoints, this API does not currently return headers like X-RateLimit-Limit or X-RateLimit-Remaining. That said, your usage is still being tracked and can be monitored through your usage dashboard: [platform.openai.com/account/usage](http://platform.openai.com/account/usage). Here are a few helpful resources that provide more context: 1. Limits: [platform.openai.com/settings/organization/limits](http://platform.openai.com/settings/organization/limits) - This page allows you to view your current usage limits and apply for increases if needed. 2. GPT Image API:help.openai[.]com/en/articles/11128753-gpt-image-api - This article provides detailed information about the GPT Image API, including its capabilities and usage. 3. Rate limits in headers: platform.openai[.]com/docs/guides/rate-limits - This guide explains how rate limits work, including details about rate-limit headers and how usage is tracked. If you have any further questions or need additional assistance, feel free to reach out, we’re here to help. Best regards, Cherry OpenAI Support ---
**Author:** ![\_j](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/_j/32/766292_2.png) [@\_j](https://community.openai.com/u/_j)\ **Post date:** [July 20, 2025, 12:29am UTC](https://community.openai.com/t/image-edits-api-not-returning-rate-limit-headers/1318889/6 "2025-07-20T00:29:34Z")
Summarized just as easily as 100 other anecdotes of attempting to get results from support: _“We will do nothing to rectify or escalate the situation. We are here to send you text that makes you stop interacting with us.”_