ACSP Suggestion 2022.11: RESTful API Improvements

Suggestion

Author: Anonymous   
Submitted On: 15 April 2022

Description: Add support for non-human “service account” users for programmatic integrations with ARIN’s RESTful API.

Value to Community: Feeds automation efforts by community at large.

Timeframe: Not specified

Status: Closed   Updated: 29 July 2026

Tracking Information

ARIN Comment

26 April 2022

Thank you for your suggestion, numbered 2022.11 upon confirmed receipt, asking that ARIN allow non-human “service accounts” to be used for programmatic interactions with ARIN¹s RESTful API.

When ARIN originally deployed the RESTful APIs, there was internal discussion about whether API keys should be managed on an individual basis, or if keys could be assigned to potentially shared role accounts. At the time, there was consensus that it was important to be able to determine which users were making changes via these APIs in the event of problems.

We agree that having the ability to use role or service accounts for programmatic interactions would be beneficial to customers, and there is minimal work needed to remove the restrictions in the system to allow this option. We will put this improvement on our list of features for prioritization.

Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented.

29 July 2026

Thank you for your suggestion, numbered 2022.11, asking that ARIN allow non-human “service accounts” to be used for programmatic interactions with ARIN’s RESTful API. On 28 July 2026, the restrictions at account creation preventing non-human “service accounts” have been removed, and ARIN now accepts such accounts.

Because this work is completed, we are closing this suggestion.

Thank you for participating in the ARIN Consultation and Suggestion Process.