Datasource is the origin of the data. Notice datasource is more or less technical term, and doesn't necessarily refer to a legal actor (e.g. vrk).
Currently we support following datasources:
In near future we will add support for following datasources:
|Package||Package defined what data customer gets from datasources. Package is also used in billing.|
|Field||a field in data source|
All change to your register are called operations. Currently following operations are supported:
|Operation batch||In order to change your information in register you must POST a operation batch to batch endpoint. Operation batch is an array of operations (see above).|
|Change batch||You you download changes from register you will get a change batch. Change batch is a snapshot of prepared changes from all datasets included in monitoring.|
|Reference Key||All person in the register must have unique reference key. If you don't give reference key, the service will generate it for the person.|
|BisnodeId||Bisnode id is Bisnode Finland's internal idenfier for a person. Bisnode id is used to track changes to person.|
|BisnodeGedi||Bisnode Gedi is Bisnode's corporate wide identifier for a person. If you use Bisnode services, for instance, in other nordic countries, you can use Bisnode Gedi as a reference to person.|
|Matching||Matching is a process where try to get BisnodeId for a person in the monitorable register.|
Register event is any changes to the data in register.
Currently we have following events:
People Monitoring REST - Implementation guide