Received-SPF: pass (google.com: domain of bounces+55753806-4e5b-tjphuhs=gmail.com@notify.openai.com designates 168.245.101.139 as permitted sender) client-ip=168.245.101.139;
Content-Type: multipart/alternative; boundary=9afd857d2407fd4be40a3cf5fbfc14eead5a40cdf4afd7a84487a13bb253
Date: Sat, 11 Apr 2026 07:38:07 +0000 (UTC)
From: Support <support@openai.com>
Mime-Version: 1.0
Message-ID: <8896ca4bfd163be97f40e8d9a3568488@openai.com>
Subject: Re: New Case
In-Reply-To: <b6cf92f5-3e77-4bb7-b3dc-b1628e0af9e2@Spark>
References: <b6cf92f5-3e77-4bb7-b3dc-b1628e0af9e2@Spark>
	<94f3ab092d78e32b1e2243634ed8c2a0@openai.com>
	<8896ca4bfd163be97f40e8d9a3568488@openai.com>
Thread-Topic: Re: New Case
To: tjphuhs@gmail.com

--9afd857d2407fd4be40a3cf5fbfc14eead5a40cdf4afd7a84487a13bb253
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0

Case Number: 07148536

Hi TJ,

Thank you for your detailed feedback, we understand your concern regarding =
being charged despite not receiving successful responses.

To investigate this further, could you please share a few additional detail=
s:

Approximate timestamps (including timezone) when the errors occurredThe mod=
els you were usingThe endpoints used (e.g., Chat Completions, Responses API=
)This will help us review your usage logs more closely and identify what ma=
y have happened.

We appreciate your cooperation and will do our best to clarify this for you=
.

Best regards,

Muhammad | OpenAI Specialist Team

Prior message

This much of a delay? I never got responses from the system. I just got API=
 errors. I didn=E2=80=99t get responses. And your errors are so generic tha=
t you can=E2=80=99t tell if there is an issue with the API key or the credi=
ts. So if you are going to charge me to send me an error response it needs =
to be note detailed so I can pinpoint the issue quicker wether it=E2=80=99s=
 a api key issue credit balance oauth issue. To get charged for you to tell=
 me you aren=E2=80=99t going to respond is absolutely rediculous. I got 0 s=
uccessful responses that day to get charged that much and for you to call i=
t a =E2=80=9Cdelay=E2=80=9D.&#160;
--9afd857d2407fd4be40a3cf5fbfc14eead5a40cdf4afd7a84487a13bb253
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=utf-8
Mime-Version: 1.0

<!--cx-email-context-start--><div data-cx-email-context=3D"true" style=3D"m=
argin-bottom:16px;padding-bottom:12px;border-bottom:1px solid #dfe1e5;font-=
size:12px;color:#5f6368;"><p style=3D"margin:0;"><strong>Case Number:</stro=
ng> 07148536</p></div><!--cx-email-context-end--><!doctype html><html><head=
><meta charset=3D"UTF-8"></head><body><p data-oa-paragraph-spacing=3D"true"=
 style=3D"margin:0;line-height:1.5;">Hi TJ,</p><p data-oa-paragraph-spacing=
=3D"true" style=3D"margin:0;line-height:1.5;"><br></p><p data-oa-paragraph-=
spacing=3D"true" style=3D"margin:0;line-height:1.5;">Thank you for your det=
ailed feedback, we understand your concern regarding being charged despite =
not receiving successful responses.</p><p data-oa-paragraph-spacing=3D"true=
" style=3D"margin:0;line-height:1.5;"><br></p><p data-oa-paragraph-spacing=
=3D"true" style=3D"margin:0;line-height:1.5;">To investigate this further, =
could you please share a few additional details:</p><ul><li>Approximate tim=
estamps (including timezone) when the errors occurred</li><li>The models yo=
u were using</li><li>The endpoints used (e.g., Chat Completions, Responses =
API)</li></ul><p data-oa-paragraph-spacing=3D"true" style=3D"margin:0;line-=
height:1.5;">This will help us review your usage logs more closely and iden=
tify what may have happened.</p><p data-oa-paragraph-spacing=3D"true" style=
=3D"margin:0;line-height:1.5;"><br></p><p data-oa-paragraph-spacing=3D"true=
" style=3D"margin:0;line-height:1.5;">We appreciate your cooperation and wi=
ll do our best to clarify this for you.</p><p data-oa-paragraph-spacing=3D"=
true" style=3D"margin:0;line-height:1.5;"><br></p><p data-oa-paragraph-spac=
ing=3D"true" style=3D"margin:0;line-height:1.5;">Best regards,</p><p data-o=
a-paragraph-spacing=3D"true" style=3D"margin:0;line-height:1.5;">Muhammad |=
 OpenAI Specialist Team</p><img src=3D"http://url3243.email.openai.com/wf/o=
pen?upn=3Du001.R2t-2BXmXa4-2BtBwkdJ0p9yJRvDuDjHfCCk5-2F2cczgKluJW-2FkXcTYTv=
-2BbCahW-2Fm-2BBK-2BdzUDsIHdHuvz6-2FWLID22B4uZzbV4nJ67h0GVS33BMG7GKbsKKI7hE=
4fBJQczUeFi8J-2FbHhQPjsCsJynAXY5KEMPhosnbNR0kcVjPC7fXqMpCrRKWRJTWPHn8h4n5n0=
-2F4-2BvU3vhWoQz8JN1SNy4ZqmbdJrfv0uRf0-2F4qIX8n1-2BMTlKLKnCjDPo7efgtrtwxY-2=
BgkncPhUlceA-2Bl45eR4CyQgEniXGJIOTwycUv8xWJfPd43-2BM3C67dgwprDyxnPY3t" alt=
=3D"" width=3D"1" height=3D"1" border=3D"0" style=3D"height:1px !important;=
width:1px !important;border-width:0 !important;margin-top:0 !important;marg=
in-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;p=
adding-top:0 !important;padding-bottom:0 !important;padding-right:0 !import=
ant;padding-left:0 !important;"/></body></html><!--cx-email-context-start--=
><div data-cx-email-context=3D"true" style=3D"margin-top:16px;padding-top:1=
2px;border-top:1px solid #dfe1e5;font-size:12px;color:#5f6368;"><p style=3D=
"margin:0 0 8px 0;"><strong>Prior message</strong></p><blockquote style=3D"=
margin:0;padding:10px 12px;border-left:3px solid #c7ccd1;background:#f7f8fa=
;color:#3c4043;white-space:pre-wrap;">This much of a delay? I never got res=
ponses from the system. I just got API errors. I didn=E2=80=99t get respons=
es. And your errors are so generic that you can=E2=80=99t tell if there is =
an issue with the API key or the credits. So if you are going to charge me =
to send me an error response it needs to be note detailed so I can pinpoint=
 the issue quicker wether it=E2=80=99s a api key issue credit balance oauth=
 issue. To get charged for you to tell me you aren=E2=80=99t going to respo=
nd is absolutely rediculous. I got 0 successful responses that day to get c=
harged that much and for you to call it a =E2=80=9Cdelay=E2=80=9D.&amp;#160=
;</blockquote></div><!--cx-email-context-end-->
--9afd857d2407fd4be40a3cf5fbfc14eead5a40cdf4afd7a84487a13bb253--