5.1.2.- Responses from DAS to OSF via notification endpoint

This page covers how WIPO DAS reports a result to an OSF over the push-notification webhook.

When this applies

Only when the OSF is configured for API-based exchange and has registered a notification URL with DAS Support. If not, the OSF must poll instead — see 5.1.3.- Responses from DAS to OSF via GET.

Payload shape

{
  "systemId": "WIPO_DAS",
  "notificationCategory": "available",
  "dateTime": "2026-10-19T10:00:00.000Z",
  "totalQuantity": 1,
  "documentRetrievalRequestStatusBag": [
    {
      "requestAckId": "USIB20260101010101",
      "requestStatusCategory": "success | pending | error",
      "errorCode": "numeric code, only present for errors",
      "statusMessage": "human-readable text"
    }
  ]
}

This is the only DAS→OSF channel that carries a numeric error code at all.

Example payloads

Success:

{
  "systemId": "WIPO_DAS",
  "notificationCategory": "available",
  "dateTime": "2026-10-19T10:00:00.000Z",
  "totalQuantity": 1,
  "documentRetrievalRequestStatusBag": [
    { "requestAckId": "USIB20260101010101", "requestStatusCategory": "success" }
  ]
}

Error — hosted OFF responded with TDA code 5 ("Not published, no authorization to permit access filed"):

{
  "systemId": "WIPO_DAS",
  "notificationCategory": "available",
  "dateTime": "2026-10-19T10:00:00.000Z",
  "totalQuantity": 1,
  "documentRetrievalRequestStatusBag": [
    {
      "requestAckId": "USIB20260101010101",
      "requestStatusCategory": "failure",
      "errorCode": "-6",
      "statusMessage": "ACCESS NOT AUTHORIZED"
    }
  ]
}

TDA/PDX code → what you receive in the notification today (office on legacy TDA/PDX)

TDA code	TDA/PDX meaning	`errorCode`	`statusMessage`
0 / 14 / 15	Successful / Registered / Updated	0	`Operation Successful`
1	Application number not found (or withdrawn/missing-field)	-7	`APPLICATION NUMBER NOT FOUND`
2	File is not available (security)	-8	`FILE WAS NOT AVAILABLE (REQUESTED APPLICATION EXISTS BUT IS NOT CLEARED FOR DISSEMINATION, e.g. security)`
3	Document(s) not found	-9	`DOCUMENT(S) WAS NOT AVAILABLE (COMPLETE SET OF REQUIRED DOCUMENTS FOR CERTIFIED COPY IS NOT AVAILABLE)`
5	Not published / no authorization	-6	`ACCESS NOT AUTHORIZED`
7	Oversize document, CD will be mailed	(none)	(none)
11	ACC invalid	-4	`INVALID DATA`
12	Request under processing	(none)	(none)
16	ACC and priority date mismatch	-15	`MISMATCH ACCESS CODE AND PRIORITY FILING DATE`
17	Priority date mismatch	-12	`MISMATCH PRIORITY FILING DATE OR ACCESS CODE`
18	ACC mismatch (or missing)	-14	`MISMATCH ACCESS CODE`
19	Priority date not provided	-13	`MISSING PRIORITY FILING DATE`
-1	System scheduled downtime	(none)	(none)
-2	System unavailable (back-end)	(none)	(none)
-6	Duplicate doc / already registered (registration only)	-1	`DUPLICATE (ENTRY ALREADY EXISTS)`

Same table, once the office migrates to the new REST interface

Once an office answers over the newer REST interface instead of TDA/PDX (see 5.1.1.- Responses from OFF to DAS (TDA/PDX codes)), the notification carries whatever errorCode/statusMessage that office's own system sends — there is no fixed numeric code on this path, and errorCode is typically left empty.

TDA/PDX code (for reference)	`errorCode` after migration	`statusMessage` after migration
0 / 14 / 15	(empty)	`ready for download` → `delivered`
1	(empty)	`document number not available`
2	(empty)	`document awaiting security clearance`
3	(empty)	`document incomplete`
5	(empty)	`document awaiting security clearance`
7	(empty)	(not applicable)
11	(empty)	`unmatched access code`
12	(empty)	`awaiting off response`
16	(empty)	`unmatched document date and access code`
17	(empty)	`unmatched document date`
18	(empty)	`unmatched access code`
19	(empty)	`invalid document details`
-1 / -2	(reported as a system error instead)	(reported as a system error instead)

Worked example — TDA code 5 ("Not published, no authorization to permit access filed"): - Today: errorCode: "-6", statusMessage: "ACCESS NOT AUTHORIZED" - After migration: errorCode: null, statusMessage: "document awaiting security clearance"

Page tree