This chapter describes the response of the TFNRegistry™ asynchronous invocations. When the user makes a call and provides a “asyncId” value, the registry will respond with a unique Message ID as part of the same request. The Message ID provided can be used by the caller to correlate the response received on the callback URL provided, after the TFNRegistry completes processing the request (see Table 2 Asynchronous Response). The following callback URL should be made available by the user to send the response (see Figure 3 Asynchronous with Response Posted to Callback URL):
https://resporg-host:port/tfnr/async/response (This is an example URL)
The Resp Org-host should be a valid host name. For example: tfnr-async.somos.com and the allowed port value is 443 and only SSL/TLS protocol is supported for added security.
Table 2: This table describes the response of the TFNRegistry Asynchronous invocations.
|
Asynchronous Response |
|
{ "errList": [ { "errMsg": "Request submitted successfully, asyncId = UATNUM2.", "errLvl": "INFO", "errCode": "099067" } ] } |
Figure 3 Asynchronous with Response Posted to Callback URL