This page covers the first hop: the raw numeric code a hosted Office of First Filing's (OFF) TDA/PDX system sends back to WIPO DAS when DAS forwards it a live retrieval or registration-acknowledgement request.
An OSF / REST API caller never sees these raw TDA/PDX codes directly. DAS always translates them before they go any further — see 5.1.2.- Responses from DAS to OSF via notification endpoint and 5.1.3.- Responses from DAS to OSF via GET for what actually reaches the caller.
Source of truth (code, not documentation): - das-app/src/app/das-tda-error-messages.ts — literal TDA/PDX message text - das-app/src/app/das-error-code-mappings.ts — the tdaSystemCodes[] arrays that map a TDA code to a DAS canonical message - das-app/src/app/das-error-codes.ts — the 6 top-level errorCode categories
TDA/PDX code → DAS canonical message
| TDA/PDX code | Status type | TDA/PDX meaning as supplied | DAS canonical message | DAS sub-code | DAS errorCode category | Notes |
|---|---|---|---|---|---|---|
| 0 | FWA-status, PDX-status | No Error / Successful | Successful. | 0 | SUCCESS | code 0 is reused for 0 / 14 / 15 |
| 1 | FWA/PDX/DAS-status | Application number provided was not found | Application number provided was not found. | -4, -7, or -5 (see note) | INVALID_INPUT_DATA or OPERATION_FORBIDDEN | ⚠️ Overloaded: the backend reuses TDA code 1 for three different outcomes depending on internal context: generic invalid input (-4), "document not found" (-7), and "document withdrawn" (-5, under OPERATION_FORBIDDEN) |
| 2 | FWA-status, PDX-status | File is not available | File is not available. (security clearance not granted) | -8 | OPERATION_FORBIDDEN | |
| 3 | PDX-status | Documents was not found | Document(s) was not found. | -9 | OPERATION_FORBIDDEN | |
| 4 | FWA-status | Document content could not be retrieved | — | (not mapped) | (none) | Not wired up in code; probably unused, as TDA 3 covers the same situation |
| 5 | PDX-status | Not published, no authorization to permit access filed | File is not available to the public, and no authorization to permit access has been filed. | -6 | OPERATION_FORBIDDEN | |
| 6 | FWA-status | Delay in translation | — | (not mapped) | (none) | Not wired up in code; probably never used (do not confuse with code -6 below, which is a different, negative code) |
| -6 | (missing from the original table entirely) | XML output processing failure (reused as a generic technical-error code) | Duplicate document received / File already uploaded and registered | -1 or -107 | INVALID_INPUT_DATA or OPERATION_FORBIDDEN | ⚠️ Actively used by the backend for two different outcomes (duplicate document vs. already-registered file), but was never documented on the old matching table |
| 7 | PDX-status | Oversize document/CD will be mailed | Oversize Document – CD will be mailed. | -201 | OPERATION_IN_PROGRESS | See 5.1.2 — no EDI translation exists for this code, so it isn't actually forwarded via the notification webhook today |
| 8 | FWA-status | Request less than 1000 pages per transaction | — | (not mapped) | (none) | Not wired up; probably unused — TDA code 7 is reported instead |
| 9 | DAS-status | Registered | — | n/a | n/a | DAS-internal status only, not a counterpart reply code from an OFF |
| 10 | DAS-status | Not Registered | — | n/a | n/a | DAS-internal only |
| 11 | PDX-status | Das Access Code invalid | ACC invalid. | -4 | INVALID_INPUT_DATA | |
| 12 | PDX-status | Request under processing, response sent later | The request is under processing, the response will be sent later. | -202 | OPERATION_IN_PROGRESS | Code comment marks this "obsolete now... not implemented on DAS side, also we don't expect it from TDA side" |
| 13 | PDX-status | Application number does not correspond with bibliographic data | — | (not mapped) | n/a | Rarely used — DAS rejects an OSF request with mismatched data before it would reach this point |
| 14 | DAS-status | Successfully Registered DAS to OFF only | Successfully Registered. | 0 | SUCCESS | |
| 15 | DAS-status | Successfully Updated DAS to OFF only | Successfully Updated. | 0 | SUCCESS | |
| 16 | DAS-status | Das Access Code and Priority Date did not match | ACC and Priority Date did not match. | -15 | INVALID_INPUT_DATA | |
| 17 | DAS-status | Priority Date did not match | Priority Date did not match. | -12 | INVALID_INPUT_DATA | |
| 18 | DAS-status | Das Access Code did not match | ACC did not match. | -14 or -13 (see note) | INVALID_INPUT_DATA | ⚠️ Overloaded: same TDA code used both for "mismatched access code" (-14) and "missing access code" (-13) |
| 19 | DAS-status | Priority Date was not provided by OFF | Priority Date was not provided by OFF. | -13 | INVALID_INPUT_DATA | |
| -1 | FWA-fault, PDX-fault | System not available, scheduled downtime | System is not available due to scheduled downtime. | -101 | DAS_SYSTEM_ERROR | |
| -2 | FWA-fault, PDX-fault | System not available, back-end problem | System is not available due to system problem. | -101 | DAS_SYSTEM_ERROR | |
| -3 | PDX-fault | Received document cannot be imported | The received document can not be imported. | -2 | INVALID_INPUT_DATA | Resolves to the "invalid document file format" sub-code, not a generic -3 |
| -4 | FWA-fault, PDX-fault | XML input processing failure | XML input processing failure | -3 | INVALID_INPUT_DATA | Covers corrupted file / invalid ST.26 package / checksum mismatch / virus infected |
| -5 | FWA-fault, PDX-fault | XML output processing failure | XML output processing failure | -3 | INVALID_INPUT_DATA | Used specifically for the "file not available" sub-case |
Known gaps / things to keep in mind when testing
- Overloaded codes (1, 18, -6) can't be told apart just from the TDA code — the real outcome depends on internal state DAS already has about the request. Don't assume a 1:1 mapping when writing test assertions.
- Unmapped codes (4, 6, 8, 9, 10, 13) exist in the ST.36/TDA specification but have no corresponding entry in
das-error-code-mappings.ts— if an OFF ever sends one of these, DAS has no specific translation for it. - Codes with no onward translation (7, 12) reach DAS but have an empty
ediSystemCodes[]entry, meaning there is currently no EDI message to forward to an OSF via the notification webhook (see 5.1.2). Code 12 is explicitly commented as obsolete.