XML-RPC is a protocol to call Webservices.nl methods using XML over HTTPS. XML-RPC is simpler than the SOAP Interface and more standardized than the HTTP-RPC Interface. XML-RPC uses XML messages that contain self-describing data structures, and does not use XML schemas to define input and output structures.
The XML-RPC interface can be found at the following locations:
UTF-8 character encoding (recommended)
Latin1 character encoding
Read more about Character Encoding. The endpoints are available on HTTPS.
Calling a method using XML-RPC consists of the following steps:
If an error occurs, you should use the X-WS-ErrorCode HTTP header to differentiate between errors.
On error, the result will be a fault containing a ‘faultCode’ and a ‘faultString’. The faultCode contains a numeric indication of the error. The values are listed in the fault code specification. The ‘faultString’ is a message explaining what went wrong. It may be useful during testing, but should not be used for detecting specific errors, as it may be subject to change in the future.
If the XML-RPC message is valid but another error occurs, such as when specifying an invalid postcode, the faultCode is -32500 and the X-WS-ErrorCode HTTP header contains the Webservices.nl error code, such as ‘Client.Input.FormatIncorrect’. This header should be used to differentiate between errors.
Besides the methods described in the documentation, the XML-RPC interface offers additional methods to retrieve meta-data on methods. With these functions, you do not have to supply your username and password.
The following example uses the OpenReact XML-RPC Client: