Web service wsdl and schemas are located here:
https://wsdfn.infoproff.com/v4/
Postman Collection (API v4) — Ready for Use:
https://www.postman.com/infoproff/infoproff-webservices/documentation/9kweer5/soap-api-v4
Postman provides a convenient way to test our API without the need to write any code. It can also automatically generate example HTTP requests for most common programming languages.
The requests generated by Postman are basic HTTP calls compatible with our SOAP API. However, for production-grade integration, we recommend using fully featured SOAP clients available in most programming languages. These clients can work directly with WSDL and XSD, automatically handling schemas, data types, and message structures.
Using a dedicated SOAP client ensures a more reliable and robust integration, reducing the likelihood of errors when constructing and parsing SOAP messages.
Authentification details
The primary authentication method is HTTP Basic Auth. Using the Authorization
header with encoded credentials is the preferred and recommended approach.
The username
corresponds to the App ID, and the password
is the associated Secret Key. These values are generated in the API Tokens section of the user dashboard and are not related to the credentials used for logging into the portal.
The authentication_block
mechanism, used in previous API versions, is still supported for backward compatibility but is considered deprecated and should not be used in new integrations.
Web service functions:
API provides several services:
The company search consists of 2 options:
The search for other countries is performed only in the database of archived reports. If you do not find the desired company, enter the company details manually.
search_result_id can be acquired here for orders with delivery_term = "o" or delivery_term = "a".
It may take up to 20 seconds to respond to a search request in the following countries: United Kingdom, Ireland, France, Spain, Portugal, Germany, Italy, Austria, Switzerland.
Norway register does not allow to search deleted companies by names. Therefore, we cannot provide a SimpleSearch by names within deleted companies in Norway.
Below you can find the example:
Below you can find the example of how to order and download reports:
To order an Online/Offline with identification report you need to receive "<search_result_id>".
To do so, please follow the link: How to search for a company?
The following statuses are used for reports:
If the execution status is Finished or Updated, then you can get an order.
The following statuses are used for reports:
If the execution status is Finished or Updated, then you can get an order.
Below you can find the example of how to order and download archived reports:
To order an archived report you need to receive "<search_result_id>" which has an "<archived_reports>" section that contains a product you need.
To do so, please follow the link: How to search for a company?
Example companies with archived reports:
Just like the online/offline reports.
Just like the online/offline reports.
Just like the online/offline reports.
Just like the online/offline reports.
To order an online financial statements, you need to receive "<search_result_id>".
To do so, please follow the link: How to search for a company?
This function is only needed when ordering a product: finances (Financial statements) with delivery_term = 'o'.
The following statuses are used for reports:
If the execution status is Finished or Updated, then you can get an order.
The request consist of 3 parts:
/report?&lang=en&doc_type=pdf¤cy_position=left&preferred_currency=EUR
https://www.infoproff.com/en/orders/files/<order_hash>/report?&lang=en&doc_type=pdf¤cy_position=left&preferred_currency=EUR
The request consist of 3 parts:
delivery_term:
These errors may occur while making request to our web service.
country_economic_overview
— includes the following subsections: data_transparency_index
, country_development_indicators
, economic_forecast
.paid_taxes
— information about taxes paid.tenders
— information about tenders.sanctions
— added to the negative_information
section. beneficiaries
, shareholders
, managers
, and employees_data
, the following element was added:source_type
— type of data source (e.g., official
, mass_media
, company_admin
, etc.). relations_of_persons
section, a new element has been added:match_type
capital
section has been restructured:capital_amount
element has been renamed to issued_capital
. number_of_shares
share_value
authorized_capital
employees_data
section:group_figure
indicates whether the data includes group-level aggregated figures (true
). source_type
specifies the data source type.is_estimated
is now included only if its value is true
. assets_data
section — consolidates previously existing sections:real_estate_data
(previously named property_data
), vehicles
, machinery_and_equipment
(previously named assets
). patents
and biological_assets
. vehicles
section, a new field has been added:value
litigations
section, the following elements have been added:content
, instance
, process
, authority
financial_statement/positions
and summary/latest_turnovers
, a new element has been added:value_origin
— describes the origin of the value; for example, the value estimated
- this value is estimated and calculated based on available data using logic or AI.branches_data
section, the following fields have been added:registration_number
director_name
Note: Minor improvements and adjustments may still occur during the stabilization phase.
A webhook is a way for an application to provide other applications with real-time information. Our webhook feature implements HTTP callbacks configured with a URL. An HTTP POST payload is sent to this URL in JSON format whenever a specified event occurs. In the context of our project, we have designed the webhook function to trigger specific events.
To set up a webhook for your application, navigate to the application settings page and look for the 'Webhooks Settings' section. And provide the following information:
After providing these details, click on 'Save'.
When an event occurs, we'll send a HTTP POST request to the payload URL with a JSON body containing information about the event.
It's important to verify that POST requests sent to the payload URL are from our application. To assist with this, every webhook request includes a X-Signature header.
For signing we use HMAC with SHA512 algorithm.
Secret is a concatenation of App ID and Secret Key from the webhooks settings.
It is possible to add your own get params to the endpoint to identify the sender if necessary.
A server must respond within 10 seconds and return a 2XX HTTP code; otherwise, webhook delivery is considered failed. In case of failure, the feature will attempt to resend the request up according delivery policy.