Tutorials

Experiment With The API Using Test Objects

The API supports ‘test objects’, which can be used to try out basic create/update/delete operations without affecting any resource management information. This tutorial walks through this process. All operations in the API follow the model described in this tutorial, so it’s useful to review this tutorial first before looking at the other material.

Create, Update and Delete Entity Objects

An ‘entity’ is a contact point, and may represent a specific person or an organizational function. Entities may be associated with a subaccount or a delegation to a subaccount. (Note that entity record data provided to the API will be mapped into Whois records and RDAP entity records, depending on the roles (‘technical’, ‘administrative’ and ‘abuse’) that are assigned to that entity.)

Create Subaccount And Provide Contact Information

A subaccount is a member of an NIR. Resources can be delegated to subaccounts and transferred between them, as well as deallocated from them. Entities can also be associated with subaccounts. The API supports the general management of subaccounts (create, update, delete).

Delegate and Deallocate INRs From APNIC’s Pool

A direct delegation is a delegation of INRs from APNIC to an NIR’s subaccount. The API supports making direct delegations from APNIC’s pool to a given subaccount, as well as deallocating those delegations as required.

Delegate And Deallocate INRs From NIR’s Pool Delegations

An NIR delegation is a delegation of INRs from one of the NIR’s pool delegations to an NIR’s subaccount. The API supports NIR delegations to a given subaccount, as well as deallocating those delegations as required. (Deallocation of an NIR delegation returns the resource to the NIR’s pool.)

Subaccounts Resource Transfer

A transfer is a movement of INRs from one account to another. The API supports moving resources from one of an NIR’s subaccounts to another of the NIR’s subaccounts.