Hello, Yes, in general, an action you can complete in OT&E should be successful in production using the same API key. The only exception would be some change that has removed the privileges of that API key – for example, if you transferred 206.16.0.0/14 to another organization today. In that case, you would be able to manage 206.16.0.0/14 in OT&E (because it’s a copy from the beginning of the month, prior to the transfer) but not in production (because the block was transferred to someone else).
Best regards, Jon Worley Technical Services Manager ARIN Registration Services https://www.arin.net/ [email protected] 703.227.0660 From: arin-tech-discuss <[email protected]> on behalf of "nyguerillagirl brainycode.com" <[email protected]> Date: Tuesday, June 20, 2017 at 2:21 PM To: "[email protected]" <[email protected]> Subject: [arin-tech-discuss] QUESTION on API Keys used in OTE vs production I am from AT&T. I tested in OTE addresses coming from a new set of IP blocks (206.16.0.0/14) that is, managing the registration of customers within this space is new to our application (but within AT&T) If my testing is successful in OTE can I assume that the API key we use in production (normal IP space we manage is 12.x.x.x) will have no issues or is there something else we should do?
_______________________________________________ arin-tech-discuss mailing list [email protected] http://lists.arin.net/mailman/listinfo/arin-tech-discuss
