This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/

[db-wg] API Documentation

Previous message (by thread): [db-wg] changes to the implementation of "abuse-c:" - final problem statement
Next message (by thread): [db-wg] API Documentation (semi solved)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Andreas Schulze andreas.schulze at datev.de
Fri Feb 17 15:18:15 CET 2017

Hello,

we like to modify RIPE objects using the API under https://rest.db.ripe.net
(OK, starting with https://rest-test.db.ripe.net)

I found some documentation:
 - https://github.com/RIPE-NCC/whois/wiki/WHOIS-REST-API-Update
 - https://www.ripe.net/manage-ips-and-asns/dns/enum/update-enum-delegation

But some points are still unclear to me.
1. Is there any documentation about the database definition, which fields an object must or may have?
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?

Thanks for help and nice weekend!
Andreas

-- 
A. Schulze
DATEV eG

Previous message (by thread): [db-wg] changes to the implementation of "abuse-c:" - final problem statement
Next message (by thread): [db-wg] API Documentation (semi solved)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]