APNIC registry API now available

In response to requests from Members seeking to enhance their experience with APNIC services, the APNIC registry API is now available. This API supports the retrieval of delegation information, as well as the management of all whois records, reverse DNS records, ROAs, and route objects. The OpenAPI specification for the API is available online.

Using the APNIC registry API, Members can now automate changes that previously required manual input. For example, when adding an announcement in BGP, a Member can use the API to create new Route Origin Authorizations (ROAs) and route objects automatically, instead of logging in to MyAPNIC to make those changes manually.

For whois records, the API supports single-object retrieval and update. For reverse DNS and abstract route management operations, the API supports a 'batch' mode of operation, where multiple changes can be submitted as a single unit. These batches take effect transactionally where possible.

All updates are managed asynchronously, by way of task objects. Once the update is submitted, the client receives a link to a task object that can be polled to check the status of the task. On completion, the task object will contain details on the outcome of the update.

All of the functionality of the API maps to functionality available in MyAPNIC. For example, changes to registered routes will take effect in MyAPNIC for the relevant account, and updates made inside MyAPNIC will be visible inside the API.

To register for an API key, log into MyAPNIC and click the 'API Keys' link under 'Resource Manager'. If you would like access to a test system, please email [email protected], and we will organize an account for you. The testbed is open to anybody interested, there's no need to be associated with an existing APNIC account or similar.

If you have API questions or feedback, you can send them to [email protected] (private) or the [email protected] mailing list (public).

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.