<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Greetings again.<br>
<br>
I almost feel like I'm a pioneer when it comes to using the new REST
API at rest.db.ripe.net, as I keep discovering things that don't
seem to align with the documentation. That aside, my most recent
experience is in regards to the /create method.<br>
<br>
When using the same payload structure as outlined at
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://rest.db.ripe.net/api-doc/path__create.html">https://rest.db.ripe.net/api-doc/path__create.html</a>
I receive an HTTP 400 response with the error message as follows:<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<pre style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Unrecognized field "whois-resources" (Class net.ripe.db.whois.api.whois.domain.WhoisResources), not marked as ignorable
at [Source: org.eclipse.jetty.server.HttpInput@17d9461b; line: 1, column: 21] (through reference chain: net.ripe.db.whois.api.whois.domain.WhoisResources["whois-resources"])
</pre>
Has the structure of the payloads changed from what is listed in the
example JSON request object or is this legitimately a bug?<br>
<div class="moz-signature">-- <br>
<br>
<span style="font-family: Arial;">
Tim Garrison<br>
Software Engineer III<br>
<br>
<b>SoftLayer, an IBM Company</b><br>
315 Capitol Street Suite 205, Houston, TX 77002<br>
281.714.4213 direct | 713.540.4325 mobile | 281.714.4657 fax |
<a class="moz-txt-link-abbreviated" href="mailto:tgarrison@softlayer.com">tgarrison@softlayer.com</a>
</span><br>
<br>
</div>
</body>
</html>