Hi Andreas You can create almost any objects you wish in the TEST Database. Keep in mind that the TEST Database is reset every day so if you want to test over a period of days keep a copy of all the base objects you need so you can easily re-create them each day. It is not a good idea to use TEST-NCC-HM-MNT. That object exists with a public password so you can authorise against it to create copies of resource objects. In the live database the resource objects would be created by the RIPE NCC and maintained by RIPE-NCC-HM-MNT. You can create your own starting pair of PERSON/MNTNER objects in the TEST Database using this: https://apps-test.db.ripe.net/db-web-ui/#/webupdates/create/person/self Once you have a PERSON and MNTNER object you can create other objects in the TEST Database using the api. cheers denis co-chair DB-WGH On 2017-02-17 15:24, Andreas Schulze wrote:
Am 17.02.2017 um 15:18 schrieb Andreas Schulze:
1. Is there any documentation about the database definition, which fields an object must or may have? https://www.ripe.net/manage-ips-and-asns/db/support/documentation
2. How are updates authenticated? I'm aware, each object has a "mntner" but how and where is the Maintainer identity part of request to the API? 3. the Test-DB did not contain any objects related to our company - that's OK. But could I add them? And how? I guess I may use 'https://apps-test.db.ripe.net/search/lookup.html?source=test&key=TEST-NCC-HM-MNT&type=mntner' Right? still unclear...
examples welcome :-)