What causes "Response indicates Failure" in MathewSachin/Captura?

Include uploadResponse.Data (status/error) in the exception text so the cause is visible.

MathewSachin/Captura · error · Exception

Response indicates Failure

Error message

Response indicates Failure

What it means

Thrown by ImgurUploader.Upload (src/Captura.Imgur/ImgurUploader.cs:54) when the deserialized ImgurUploadResponse has Success == false. The HTTP request itself succeeded and parsed as JSON, but the Imgur v3 API signalled a logical failure in the response body. The Data payload (status/error) holds the reason, which this throw discards.

Source

Thrown at src/Captura.Imgur/ImgurUploader.cs:54

            w.Headers.Add("Authorization", await GetAuthorizationHeader());

            NameValueCollection values;

            using (var ms = new MemoryStream())
            {
                Image.Save(ms, Format);

                values = new NameValueCollection
                {
                    { "image", Convert.ToBase64String(ms.ToArray()) }
                };
            }

            var uploadResponse = await UploadValuesAsync<ImgurUploadResponse>(w, "https://api.imgur.com/3/upload.json", values);

            if (!uploadResponse.Success)
            {
                throw new Exception("Response indicates Failure");
            }

            return new UploadResult
            {
                Url = uploadResponse.Data.Link,
                DeleteLink = $"https://api.imgur.com/3/image/{uploadResponse.Data.DeleteHash}"
            };
        }

        async Task<string> GetAuthorizationHeader()
        {
            if (_settings.Anonymous)
            {
                return $"Client-ID {_apiKeys.ImgurClientId}";
            }

            if (string.IsNullOrWhiteSpace(_settings.AccessToken))
            {

View on GitHub (pinned to 3fdf41529b)

Solutions

Include uploadResponse.Data (status/error) in the exception text so the cause is visible.
Check the Imgur rate-limit response headers and back off / queue the upload.
Verify the API key (anonymous) or re-authenticate (OAuth) when the body indicates auth failure.
Reduce image size or re-encode to PNG/JPEG before upload.

Example fix

// before
if (!uploadResponse.Success) throw new Exception("Response indicates Failure");
// after
if (!uploadResponse.Success)
    throw new Exception($"Imgur upload failed (status {uploadResponse.Status}): {uploadResponse.Data?.Error}");

Defensive patterns

Strategy: try-catch

Validate before calling

// pre-check rate limits via Imgur response headers before uploading large payloads
// (no body field exists pre-upload; rely on tracking remaining credits from prior responses)

Try / catch

try { var r = await uploader.Upload(img, fmt, progress); }
catch (Exception e) when (e.Message.Contains("Response indicates Failure")) { /* back off, check keys/token, shrink image */ }

Prevention

Include uploadResponse.Data in the exception so the failure reason is visible.
Respect Imgur rate-limit headers and queue uploads when near the cap.
Re-encode very large images to PNG/JPEG and cap dimensions before upload.

When it happens

Trigger: POST to https://api.imgur.com/3/upload.json returned JSON with success=false. Imgur returns this for rate limiting (429 mapped into the body), over-capacity, image too large/unsupported, banned client, or an invalid/revoked API key/token.

Common situations: Anonymous uploads hitting the per-IP/per-app rate cap; an image format Imgur rejects; an expired or revoked OAuth token used after the bearer header was set; Imgur service degradation returning a soft failure.

Related errors

AI-assisted analysis of MathewSachin/Captura@3fdf41529b (2026-08-13). Data as JSON: /api/errors/340286c5673eaf08. Report an issue: GitHub.