The Objectypes API works together with the Objects API: Objects are of a certain objecttype. In the examples below, there is an objecttype tree that is considered the national definition. The objecttype is therefore present in the national Objecttypes API, hosted by a public national organization, such as the VNG.

The municipality of Utrecht wants to store its trees according to the national definition and indicates that the trees in its Objects API follow the objecttype tree as provided in the Objecttypes API by VNG.

As soon as the municipality of Utrecht authorizes this, trees can immediately be stored in their Objects API.

Municipality of Utrecht using its own Objects API to store trees according to the definitions from the VNG Objecttypes API.

Not only the municipality of Utrecht can do this. Many more organizations can do this and store the trees that are relevant for them according to this definition.

More organizations store their trees according to the national definition.

Every organization is free to decide which objecttypes to use but also, which Objecttypes API to use. It’s supported to run your own Objecttypes API with your own objecttypes. This is useful if you want to deviate from national standards or want to use other objecttypes that are not available in the national Objecttypes API.

In the case below, the municipality of Amsterdam decides to use their own objecttype of a tree. They run their own Objecttypes API with that specific objecttype in it.

Municipality of Amsterdam using its own Objecttypes API.

Eventually, the Objects API will contain objects of many different objecttypes that can come from many different Objecttypes API.

Mixing Objecttypes API in your Objects API