---
title: "Get Fred Diagnostic"
method: GET
path: "/api/admin/fred-diagnostic"
tags: ["Admin"]
---

# Get Fred Diagnostic

`GET /api/admin/fred-diagnostic`

## Request

- Base URL: `https://api.xfinlab.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.xfinlab.com/api/admin/fred-diagnostic`
- Auth: none declared

2026-08-26 (debugging the persistent RRPONTSYD/M2SL/WALCL HTTP 400
surfaced by the new Data Factory error tracking): AJ manually
replicated the exact same request (same series_id, same api_key,
same params) via his own browser and it succeeded -- meaning the
request shape and the key value HE tested are both fine. Re-pasting
the key into Railway's env var didn't clear the error either. This
endpoint runs the IDENTICAL request server-side, from inside the
actual Railway process, and returns FRED's real response instead of
another layer of guessing. Never echoes the key itself -- only its
length and whether it has leading/trailing whitespace (a very common
real cause of this exact symptom: an invisible copy-paste artifact
that works fine when a browser trims it but not when sent raw over
HTTP), plus FRED's actual status code and response body for the
RRPONTSYD call so we can see FRED's own error message text.

## Query parameters

- `token` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/xfinlab/apis/xfinlab-api.md) · [All operations](https://skmtc.dev/xfinlab/apis/xfinlab-api/llms.txt) · [OpenAPI document](https://skmtc.dev/xfinlab/apis/xfinlab-api/revisions/205f85614bc6?raw)