<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Hello Tim,</div>
<div><br>
</div>
<div>If I'm understanding you correctly, you want to do a GET on a detailed reassignment to a customer via the Reg-RWS API.</div>
<div><br>
</div>
<div>The way to accomplish this would be to create the POC handles for the customer's Org ID using the MAKELINK parameter in the POC "Create" method. Specifying MAKELINK as TRUE links your ARIN Online account to the POC handle, which allows you manage it as
well as any Org IDs and any reassignments associated with that Org ID. You then create an Org ID for the customer using the "Create Recipient ORG" method, then create the detailed reassignment. You should then be able to do a GET on the customer's reassignment.</div>
<div><br>
</div>
<div>The basic rationale for this is that the Reg-RWS API returns information that may not be publicly visible, whereas Whois-RWS does not. In general, only a web user that's directly linked to a given object can view it, to protect any private information
that wouldn't ordinarily be visible to the general public. The MAKELINK parameter is a way to designate that this record is created to be managed by an upstream ISP, which allows the ISP to view and modify it.</div>
<div><br>
</div>
<div>Obviously this would only be useful for records created in this manner, so for detailed reassignments created outside the Reg-RWS API (or ones created within it without the MAKELINK parameter specified as TRUE), you'll run into the same problem you described
below. One idea would be to delete the existing records and recreate them using the MAKELINK parameter. That would be some work and might not be an acceptable solution to you, but it would allow you to start with a clean slate that allows you to manage your
records in the manner you desire.</div>
<div><br>
</div>
<div>That's the way the API works today. If you want to propose a change to the way the service works (aside from posting to this list, obviously), you can formally submit your suggestion via the process documented at:</div>
<div><br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span><a href="https://www.arin.net/app/suggestion/">https://www.arin.net/app/suggestion/</a></div>
<div><br>
</div>
<div>
<div>
<div>
<div>
<div>If you have any further questions, comments, or concerns please respond to this message or contact me directly. </div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Jon Worley</div>
<div>Senior Resource Analyst</div>
<div>ARIN Registration Services</div>
<div>https://www.arin.net/</div>
<div>hostmaster@arin.net</div>
<div>703.227.0660</div>
</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Tim Garrison <<a href="mailto:tgarrison@softlayer.com">tgarrison@softlayer.com</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, September 17, 2013 4:04 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:arin-tech-discuss@arin.net">arin-tech-discuss@arin.net</a>" <<a href="mailto:arin-tech-discuss@arin.net">arin-tech-discuss@arin.net</a>><br>
<span style="font-weight:bold">Subject: </span>[arin-tech-discuss] Detailed Reassignment Permissions<br>
</div>
<div><br>
</div>
<div>
<div text="#000000" bgcolor="#FFFFFF">Greetings,<br>
<br>
I apologize if this has been addressed in a previous thread. <br>
<br>
I am working on reconciling some information between a local database and what has been registered with the ARIN RESTful API. The problem I'm coming across though is in the case of detailed reassignments. Where the 'net' has been reassigned to an 'org', I can
do absolutely nothing other than 'delete' the reassignment; even simple 'get' requests are failing with an HTTP 401.<br>
<br>
This would make sense if the restriction on these objects was global. However, I am able to access the objects just the same using the WHOIS search form at
<a class="moz-txt-link-freetext" href="http://whois.arin.net">http://whois.arin.net</a>.<br>
<br>
It would make sense if further reassignments or allocations on these objects was restricted once they were reassigned, but it is my belief that if it's available via the public search tools, it should also be available in the API. I really don't want to have
to modify my application to use both APIs in this case.<br>
<br>
If there is no documented business rule for this restriction, could we please get it lifted?<br>
<br>
Thanks,<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>
</div>
</div>
</span>
</body>
</html>