What this shows

This example matters because API auth failures are common and noisy; automating triage captures context and routes actionable issues to your repo quickly.

Raw feedback

User message

Getting a 401 when I POST to /api/v1/ingest with my key — used the same header as before, now it just fails. Please advise, it's blocking uploads.

Triage output

Structured result

{
    "type": "bug",
    "severity": "high",
    "title": "401 Unauthorized on API ingest",
    "summary": "User receives 401 Unauthorized when posting feedback to the ingest endpoint using their API key.",
    "tags": [
        "api",
        "auth",
        "ingest",
        "401",
        "bug"
    ],
    "sentiment": "frustrated",
    "confidence": 0.93
}

Resulting issue

github

401 Unauthorized when POSTing to /api/v1/ingest

Raw user message: "Getting a 401 when I POST to /api/v1/ingest with my key — used the same header as before, now it just fails. Please advise, it's blocking uploads." Steps to reproduce: 1. POST to https://triagefast.app/api/v1/ingest 2. Include header Authorization: Bearer <user_key> 3. Send feedback payload Actual: 401 Unauthorized returned. Expected: 200 OK and triage accepted. Notes: User reports this previously worked. Verify key validity and auth middleware logs; check for recent token revocations or header parsing changes.

Live example

Use the API directly

Send the same raw message to TriageFast and get the structured result back through the normal ingest endpoint.

curl -X POST https://triagefast.app/api/v1/ingest -H "Authorization: Bearer tf_live_xxxx" -H "Content-Type: application/json" -d '{"message":"Getting a 401 when I POST to /api/v1/ingest with my key — used the same header as before, now it just fails. Please advise, it's blocking uploads."}'

How it works

Step 1

Send the message

POST the raw feedback to the ingest endpoint with your Bearer key.

Step 2

TriageFast classifies it

AI extracts structured fields like type, severity, title, summary, tags, sentiment, and confidence.

Step 3

Structured output appears in github

TriageFast routes the generated issue to GitHub within ~30 seconds.

Related examples

API auth failure (401) routed to GitHub as bug