Types of Web Services

The Pro6PP data are available through the following types of Web services:

• Web API

  The REST API is best used with websites. The easy HTTP GET/POST methods provide a JSON or XML result. Advised in combination with web (JavaScript) and script (Python, Ruby, PHP) languages.

• SOAP

  The SOAP webservice integrates well using traditional languages and makes using a webservice easy. Advised in combination with .NET (C#/VB) or Java.

Web API

Using a simple HTTP GET or POST method, an API call is performed.

undefined/v1/METHOD

On the spot of METHOD one of the available methods need to be filled in.

Each method has at least one required parameter that needs to be sent along with each call:

• auth_key: this key is received by email when signing up for a Pro6PP account.

For each API call, these optional parameters may be submitted:

• format: pass on the desired output format. ’xml’ or ’json’ (default).
• pretty: for a slight performance advantage, the output is unformatted by default. Set to ’True’ and receive developer readable output.

Each specific method can take additional required or optional parameters.

SOAP

Using this WSDL in Document/literal style, the SOAP 1.1 compatible webservice can be used.

Note that not all of our endpoints are exposed through SOAP currently. Please let us know if you’re missing any.

1.4

undefined/v1.4/soap/api.wsdl

Changes since 1.3:

• New field in endpoint suggest: municipality
• New fields in endpoint NL autocomplete: surface, functions, construction_year

1.3

undefined/v1.3/soap/api.wsdl

Changes since 1.2:

• Updated endpoint autocomplete for Belgium

1.2

undefined/v1.2/soap/api.wsdl

Changes since 1.1:

• New field in endpoint autocomplete: street_nen5825

1.1 (deprecated)

undefined/v1.1/soap/api.wsdl

Changes since 1.0:

• Use HTTPS endpoints
• New fields in endpoint autocomplete: streetnumber, extension

1.0 (deprecated)

First version:

undefined/v1/soap/api.wsdl