Method:
DataTools.Enhance.Address.SuppressionDeceased.AuPost.AppendToDpid
Use to retrieve information indicating when someone has passed away at a DPID associated with an Australian address.
Test:
Input Parameters:
Output Fields:
Field | Description |
DPID | Delivery Point ID |
DeceasedDate | Date provided that someone passed away at the associated address. Format yyyy-mm-dd |
Supported Web Service API Interfaces:
Web Service Method: ProcessQueryStringRequest (REST with QueryString)
Request Format: Url QueryString, Body (x-www-form-urlencoded),
Response Formats: JSON, XML*,
Protocols: HTTP GET, HTTPS GET, HTTP POST, HTTPS POST, HTTP OPTIONS, HTTPS OPTIONS
Example Server Path: https://customname.datatoolscloud.net.au/KleberWebService/DtKleberService.svc
Sample QueryString Request:
/ProcessQueryStringRequest?Method=DataTools.Enhance.Address.SuppressionDeceased.AuPost.AppendToDpid&DPID=&RequestId=&RequestKey=&DepartmentCode=
Sample JSON Response:
{
"DtResponse":{
"RequestId":"",
"ResultCount":"1",
"ErrorMessage":"",
"Result":[
{
"DPID":"",
"DeceasedDate":""
}
]
}
}
Web Service Method: ProcessQueryJsonRequest (REST with JSON)
Request Format: Body (Raw JSON),
Response Formats: JSON, XML*,
Protocols: HTTP GET, HTTPS GET, HTTP POST, HTTPS POST, HTTP OPTIONS, HTTPS OPTIONS
Example Server Path: https://customname.datatoolscloud.net.au/KleberWebService/DtKleberService.svc
Single Request
Sample JSON Request:
{
"DtRequest":{
"Method":"DataTools.Enhance.Address.SuppressionDeceased.AuPost.AppendToDpid",
"DPID":"",
"RequestId":"",
"RequestKey":"",
"DepartmentCode":""
}
}
Sample JSON Response:
{
"DtResponse":{
"RequestId":"",
"ResultCount":"1",
"ErrorMessage":"",
"Result":[
{
"DPID":"",
"DeceasedDate":""
}
]
}
}
Multiple Requests
Sample JSON Request:
{
"DtRequests":{
"DtRequest":[
{
"Method":"DataTools.Enhance.Address.SuppressionDeceased.AuPost.AppendToDpid",
"DPID":"",
"RequestId":"",
"RequestKey":"",
"DepartmentCode":""
},
{
"Method":"DataTools.Enhance.Address.SuppressionDeceased.AuPost.AppendToDpid",
"DPID":"",
"RequestId":"",
"RequestKey":"",
"DepartmentCode":""
}
]
}
}
Sample JSON Response:
{
"DtResponses":{
"ErrorMessage":"",
"DtResponse":[
{
"RequestId":"",
"ResultCount":"1",
"ErrorMessage":"",
"Result":[
{
"DPID":"",
"DeceasedDate":""
}
]
},
{
"RequestId":"",
"ResultCount":"1",
"ErrorMessage":"",
"Result":[
{
"DPID":"",
"DeceasedDate":""
}
]
}
]
}
}
Web Service Method: ProcessQueryXmlRequest (REST with XML)
Request Format: Body (Raw XML),
Response Formats: JSON, XML*,
Protocols: HTTP GET, HTTPS GET, HTTP POST, HTTPS POST, HTTP OPTIONS, HTTPS OPTIONS
Example Server Path: https://customname.datatoolscloud.net.au/KleberWebService/DtKleberService.svc
Single Request
Sample XML Request:
<DtRequest Method="DataTools.Enhance.Address.SuppressionDeceased.AuPost.AppendToDpid" DPID="" RequestId="" RequestKey="" DepartmentCode="" />
Sample XML Response:
<DtResponse RequestId="" ResultCount="1" ErrorMessage="">
<Result DPID="" DeceasedDate="" />
</DtResponse>
Multiple Requests
Sample XML Request:
<DtRequests>
<DtRequest Method="DataTools.Enhance.Address.SuppressionDeceased.AuPost.AppendToDpid" DPID="" RequestId="" RequestKey="" DepartmentCode="" />
<DtRequest Method="DataTools.Enhance.Address.SuppressionDeceased.AuPost.AppendToDpid" DPID="" RequestId="" RequestKey="" DepartmentCode="" />
</DtRequests>
Sample XML Response:
<DtResponses ErrorMessage="">
<DtResponse RequestId="" ResultCount="1" ErrorMessage="">
<Result DPID="" DeceasedDate="" />
</DtResponse>
<DtResponse RequestId="" ResultCount="1" ErrorMessage="">
<Result DPID="" DeceasedDate="" />
</DtResponse>
</DtResponses>
* Add the additional input parameter "OutputFormat=json" or "OutputFormat=xml" to change the response format from default.
* Add the additional input parameter "callback" to convert JSON responses to JSONP responses for across domains support.
CORS header included where callback is not defined.
Please Note:
Ensure you thoroughly test all the methods you are using and are happy with the results before going into production. DataTools is charged by the data suppliers for use of every method – therefore
ALL calls to any method will incur a COST. When you register DataTools provides you with free credit to help with development and trialling of the service. Once that credit is used you will need to purchase a monthly subscription and/or top up to continue using the service, even for development purposes. Please check the Method Pricing List for all current costs. DataTools does not warrant or guarantee the quality of the results returned and will not be held responsible for any costs incurred by using a method. Should you have any questions please contact your Sales representative or the Client Services team.