...
There is no numeric errorCode field anywhere in the polling responses. The only channel that carries one is the push notification webhook (see 5.1.2). What you do get is a free-text requestStatusMessage, sourced from das-status.ts.
...
- If the failure was raised by DAS's own validator (e.g. an OSF polls a retrieval it submitted with a mismatched access code) → you'll see the literal strings above (e.g.
unmatched access code). - If the failure originated from a hosted OFF answering over TDA/PDX →
requestStatusMessageis overwritten with the EDI-translated text documented on 5.1.2 (e.g."ACCESS NOT AUTHORIZED"for TDA code 5), becauseOSF_LAST_MESSAGEis set to that EDI string regardless of which channel (push or pull) ends up reading it.
...
| Field you see | Where it's documented |
|---|---|
code, details[].code, details[].message (HTTP 4xx on submission) | This page, section A |
requestStatusCategory, requestStatusMessage (HTTP 200 on poll) | This page, section B |
errorCode, statusMessage (push notification body) | 5.1.2.- Responses from DAS to OSF via notification endpoint |
| Raw TDA/PDX numeric code (OFF→DAS only, never seen by the OSF directly) | 5.1.1.- Responses from OFF to DAS (TDA/PDX codes) |