Automating Your Workflow Using the IRR RESTful API

ARIN provides a way to automate creation and maintenance of Internet Routing Registry (IRR) records using an application programming interface (API) to ARIN’s database. You can use Representational State Transfer (REST) commands to add, update, or delete routing objects. These commands (also known as REST calls) are entered in a script or configured on the back end of a custom software program and are then submitted to the ARIN database to create, view, update, or delete records. RESTful commands are structured to include the following:

  • the command method (such as GET, POST, and PUT)
  • a URL, or address of the RESTful server
  • other information, including your API key

Some REST calls require you to format and send information to ARIN with your command in a formatted “payload” file, or message body. With IRR REST commands, these payloads are sent in Routing Policy Specification Language (RPSL) format. (More information about RPSL is available in RFC 2622).

The IRR RESTful service is part of ARIN’s suite of REST commands known as Reg-RWS that are used for tasks such as updating registration information for IP addresses and ASNs or reporting transferred resources. IRR REST commands currently accept data (payloads) in RPSL format. Reg-RWS accepts payloads in XML format.

Transitioning from IRR-email

If you decide to move from using email templates for IRR to using the RESTful API, you’ll need to reconfigure the processes that you normally use to create, update, and delete IRR objects. For example, some organizations may have automated processes that accept routing object changes and send those changes in a template via email to ARIN. Those processes will need to be changed to connect to ARIN’s IRR API using the RESTful commands described in this document. However, the actual format (RPSL) of your underlying routing data will not change, as the IRR RESTful API accepts routing data in RPSL format. Visit Converting IRR Email Templates to REST Commands for more information.

Note for IRR-Online Users

Currently, IRR objects that are created in IRR-Online (in the ARIN Online IRR Object Records menu) are not able to be viewed, edited, or updated using the RESTful API.

IRR REST Commands: Format and Example

IRR REST commands (also referred to as “calls”) generally have the format of method /URL/<object>/<objectID>/<objectName>?apikey=<api-key> where:

  • method is one of the following:
    • GET retrieves information about a record
    • POST creates a new record
    • PUT modifies an existing record
    • DELETE deletes a record
  • URL is the address of ARIN’s IRR RESTful server, https://reg.arin.net/rest/irr
  • object is the type of IRR object:
    • route
    • route6
    • aut-num
    • as-set
    • route-set
  • <objectID> is the identifying information for the object. This can contain multiple parts divided by the / character (for example, the IP address block, in CIDR format, of a route would have a / character in between the IP address and prefix length, or block size).
  • <objectName> is the name you have given the object
  • <api-key> is your API key that was configured using the Settings > Security Info > Manage API Keys option in ARIN Online. Visit API Keys for more information.

Note: The commands to create as-set and route-set objects are slightly different in that they append &orgHandle=HANDLE to the end of the command; this is explained in the description of these commands.

To give an example of a typical command, the following command creates a route6 object:

POST https://reg.arin.net/rest/irr/route/2001:db8::/32/AS65536?apikey=APIKEY

REST commands also require headers and sometimes, when you’re creating an object, require a payload or a message body that contains the information of the object you’re creating in RPSL format. Commands that require a payload are noted in this document.

Headers

IRR REST commands require these headers be used in your scripts or REST client software.

For all calls:

Accept: application/rpsl

For calls which include a payload, or body message:

Accept: application/rpsl
Content-Type: application/rpsl

Payloads

Some commands require that you send a payload, or message body, with the command. This payload must be in RPSL format and contain the appropriate attributes and values for that object. The following is an example of the payload required for the route-set object:

route-set: RS-ARIZONA
members: 2001:db8::/32
descr: Example Corp LLC Arizona 1
tech-c: EXAMPLETECH-ARIN
admin-c: EXAMPLEADMIN-ARIN
remarks: This is an example.
mnt-by: MNT-EXAMPLECORP
source: ARIN

Note the following when constructing payloads:

  • The mnt-by field is the prefix MNT and the Org ID of the organization that configures (maintains) the IRR object and manages the resource that is specified in the route object. It is in the format MNT-OrgID; for example, MNT-SAMPLEORG. The mnt-by field for new IRR records created using IRR-Online or IRR REST commands no longer has any relationship to legacy maintainer objects that were migrated from ARIN’s previous IRR system in June 2020.
  • The source field value must be ARIN.

Automation and Batch Processing

Multiple REST calls can be grouped together to automate creating, updating, and deleting IRR objects with a single script, or scripts can be set up to automatically send individual REST calls to ARIN. For example, you might configure scripts on the back end of your custom network software that send REST commands to ARIN whenever route objects are created, when the name of a route is changed, or when a route is deleted. Currently, only one action is supported in a single REST call. Batch processing, or performing multiple actions with a single REST call, is not yet implemented.

Objects

The following sections list the types of objects and how to create, view, edit, and delete the object.

route and route6 Objects

route objects are created for IPv4 routes and route6 objects are created for IPv6 routes. The only difference between these objects (aside from the type of IP address) is the payload content.

Creating a route Object

This call creates a route object. These objects specify the IPv4 address block and the ASN of the autonomous system from which the route originates.

Method: POST
URL: /rest/irr/route/IPAddress/prefixLength/originAS?apikey=APIKEY
Header:

Content-Type: application/rpsl
Accept: application/rpsl
Content: Payload in RPSL format that contains the following:

  • route: The IP address and prefix length, in CIDR format, of the route to be originated. Together with the origin: attribute, constitutes the primary key of the route object.
  • origin: The ASN from which the route originates.
  • descr: In the description, enter any information you think needs to be here. This could be your name and address, your ISP’s name, or a network name or location.
  • admin-c: Admin POC for the organization that is maintaining the object. This field is the exact POC Handle as shown in Whois for the Org ID.
  • tech-c: Tech POC for the organization that is maintaining the object. This field is the exact POC Handle as shown in Whois for the Org ID.
  • mnt-by: The prefix MNT and the Org ID of the organization that configures (maintains) the IRR object and manages the resource that is specified in the route object. It is in the format MNT-OrgID; for example, MNT-SAMPLEORG.
  • source: ARIN  Do not use any other value; all objects must have this line.

Command Example:

POST https://reg.arin.net/rest/irr/route/192.0.2.0/24/AS65536?apikey=API-1234-5678-2222-3333

Payload Example:

route: 192.0.2.0/24
origin: AS65536
descr: Example Corp LLC Arizona 1
admin-c: EXAMPLEADMIN-ARIN
tech-c: EXAMPLETECH-ARIN
mnt-by: MNT-EXAMPLECORP
source: ARIN

Returns:

200 OK response and RPSL of the created object.


Creating a route6 Object

This call creates a route6 object. These objects specify the IPv6 address block and the ASN of the autonomous system from which the route originates.

Method: POST
URL: /rest/irr/route/IPAddress/prefixLength/originAS?apikey=APIKEY
Header:

Content-Type: application/rpsl
Accept: application/rpsl
Content: Payload in RPSL format that contains the following:

  • route6: The IP address and prefix length, in CIDR format, of the route to be originated. Together with the origin: attribute, constitutes the primary key of the route6 object.
  • origin: The ASN from which the route originates.
  • descr: In the description, enter any information you think needs to be here. This could be your name and address, your ISP’s name, or a network name or location.
  • admin-c: Admin POC for the organization that is maintaining the object. This field is the exact POC Handle as shown in Whois for the Org ID.
  • tech-c: Tech POC for the organization that is maintaining the object. This field is the exact POC Handle as shown in Whois for the Org ID.
  • mnt-by: The prefix MNT and the Org ID of the organization that configures (maintains) the IRR object and manages the resource that is specified in the route6 object. It is in the format MNT-OrgID; for example, MNT-SAMPLEORG.
  • source: ARIN  Do not use any other value; all objects must have this line.

Command Example:

POST https://reg.arin.net/rest/irr/route/2001:db8::/32/AS65536?apikey=API-1234-5678-2222-3333

Payload Example:

route6: 2001:db8::/32
origin: AS65536
descr: Example Corp LLC Arizona 1
admin-c: EXAMPLEADMIN-ARIN
tech-c: EXAMPLETECH-ARIN
mnt-by: MNT-EXAMPLECORP
source: ARIN
Returns:

200 OK response and RPSL of the created object.


Viewing a route or route6 Object

This call gets information about a route or route6 object. (Note that at this time, IRR objects created in IRR-Online cannot be viewed using the RESTful API.)

Method: GET
URL: /rest/irr/route/IPAddress/prefixLength/originAS?apikey=APIKEY
Header:

Accept: application/rpsl
Content: None
Command Example:

GET https://reg.arin.net/rest/irr/route/192.0.2.0/24/AS65536?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the object.


Modifying a route Object

This call modifies an existing route object. (Note that at this time, IRR objects created in IRR-Online cannot be modified using the RESTful API.)

Method: PUT
URL: /rest/irr/route/IPAddress/prefixLength/originAS?apikey=APIKEY
Header:

Accept: application/rpsl
Content-Type: application/rpsl
Content: Payload as described in Creating a route Object
Command Example:

PUT https://reg.arin.net/rest/irr/route/192.0.2.0/24/AS65536?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the object.


Modifying a route6 Object

This call modifies an existing route6 object. (Note that at this time, IRR objects created in IRR-Online cannot be modified using the RESTful API.)

Method: PUT
URL: /rest/irr/route/IPAddress/prefixLength/originAS?apikey=APIKEY
Header:

Accept: application/rpsl
Content-Type: application/rpsl
Content: Payload as described in Creating a route6 Object
Command Example:

PUT https://reg.arin.net/rest/irr/route/2001:db8::/32/AS65536?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the object.


Deleting a route or route6 object

This call deletes a route or route6 object. (Note that at this time, IRR objects created in IRR-Online cannot be deleted using the RESTful API.)

Method: DELETE
URL: /rest/irr/route/IPAddress/prefixLength/originAS?apikey=APIKEY
Header:

Accept: application/rpsl
Content: None
Command Example:

DELETE https://reg.arin.net/rest/irr/route/192.0.2.0/24/AS65536?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the deleted object.


aut-num Objects

Creating an aut-num Object

This call creates an aut-num object. These objects specify an ASN and define its routing policies using the fields in the record.

Method: POST
URL: /rest/irr/aut-num/ASN?apikey=APIKEY
Header:

Content-Type: application/rpsl
Accept: application/rpsl
Content: Payload in RPSL format that contains the following:

  • aut-num: The ASN for the routing policy.
  • as-name: An alphanumeric identifier for the aut-num object.
  • descr: In the description, enter any information you think needs to be here. This could be your name and address, your ISP’s name, or a network name or location.
  • admin-c: Admin POC for the organization that is maintaining the object. This field is the exact POC Handle as shown in Whois for the Org ID.
  • tech-c: Tech POC for the organization that is maintaining the object. This field is the exact POC Handle as shown in Whois for the Org ID.
  • mnt-by: The prefix MNT and the Org ID of the organization that configures (maintains) the IRR object and manages the resource that is specified in the route object. It is in the format MNT-OrgID; for example, MNT-SAMPLEORG.
  • source: ARIN  Do not use any other value; all objects must have this line.
  • member-of: The as-set (one or more) to which the object belongs. The as-set objects that are listed also need to include the maintainer associated with this aut-num in their object record for the cross reference to work.
  • import: Indicates the ASNs of the peers from which your AS will receive routing information and describes the routing information you’ll accept. For example, you can configure your routing to import a set of routes from a specific ASN that matches a filter, such as an IPv4 address. You can also specify actions to set or modify route attributes (such as assigning a preference to a route). More information is available in Section 6.1 of RFC 2622. (The mp-import field extends this function for IPv6.)
  • export: Describes export policies (for example, exporting or announcing a set of routes or routes that match a filter) to specified ASes. More information is available in Section 6.2 of RFC 2622. (The mp-export field extends this function for IPv6.)
  • default: Specifies the default routing policy (for example, if the AS should default to another AS for routing and under which conditions, such as if a specific filter is matched). More information is available in Section 6.5 of RFC 2622. (The mp-default field extends this function for IPv6.)
  • mp-import: Describes import policies as in the “import” field, but extends RPSL to allow “multi-protocol” routing policy. More information is available in Section 2.5 of RFC 4012.
  • mp-export: Describes export policies as in the “export” field, but extends RPSL to allow “multi-protocol” routing policy. More information is available in Section 2.5 of RFC 4012.
  • mp-default: Specifies the default routing policy as in the “default” field, but extends RPSL to allow “multi-protocol” routing policy. More information is available in Section 2.5 of RFC 4012.

Command Example:

POST https://reg.arin.net/rest/irr/aut-num/AS65536?apikey=API-1234-5678-2222-3333

Payload Example:

aut-num: AS65536
as-name: AS-ARIZ-NODE1
descr: Example Corp LLC Arizona 1
import: from AS65540 accept ANY
export: to AS65550 announce ANY
admin-c: EXAMPLEADMIN-ARIN
tech-c: EXAMPLETECH-ARIN
mnt-by: MNT-EXAMPLECORP
source: ARIN

Returns:

200 OK response and RPSL of the created object.


Viewing an aut-num Object

This call gets information about an aut-num object. (Note that at this time, IRR objects created in IRR-Online cannot be viewed using the RESTful API.)

Method: GET
URL: /rest/irr/aut-num/ASN?apikey=APIKEY
Header:

Accept: application/rpsl
Content: None
Command Example:

GET https://reg.arin.net/rest/irr/aut-num/AS65536?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the object.


Modifying an aut-num Object

This call modifies an existing aut-num object. (Note that at this time, IRR objects created in IRR-Online cannot be modified using the RESTful API.)

Method: PUT URL: /rest/irr/aut-num/ASN?apikey=APIKEY
Header:

Accept: application/rpsl
Content-Type: application/rpsl

Content: Payload as described in Creating an aut-num Object.
Command Example:

PUT https://reg.arin.net/rest/irr/aut-num/AS65536?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the modified object.


Deleting an aut-num Object

This call deletes an aut-num object. (Note that at this time, IRR objects created in IRR-Online cannot be deleted using the REST API.)

Method: DELETE
URL: /rest/irr/aut-num/ASN?apikey=APIKEY
Header:

Accept: application/rpsl
Content: None
Command Example:

DELETE https://reg.arin.net/aut-num/AS65536?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the deleted object.


as-set Objects

Creating an as-set Object

This call creates an as-set object. These objects specify a set of ASNs through which traffic can be routed. The members of the set can also include other as-set names.

Method: POST
URL: /rest/irr/as-set?apikey=APIKEY&orgHandle=HANDLE
Header:

Content-Type: application/rpsl
Accept: application/rpsl
Content: Payload in RPSL format that contains the following:

  • as-set: A name you give to a group of ASNs. Begins with AS-.
  • descr: In the description, enter any information you think needs to be here. This could be your name and address, your ISP’s name, or a network name or location.
  • admin-c: Admin POC for the organization that is maintaining the object. This field is the exact POC Handle as shown in Whois for the Org ID.
  • tech-c: Tech POC for the organization that is maintaining the object. This field is the exact POC Handle as shown in Whois for the Org ID.
  • mnt-by: The prefix MNT and the Org ID of the organization that configures (maintains) the IRR object and manages the resource that is specified in the route object. It is in the format MNT-OrgID; for example, MNT-SAMPLEORG.
  • source: ARIN  Do not use any other value; all objects must have this line.
  • remarks: Any additional information the creator of the objects wants to provide (this information will also be published in the IRR database).
  • members: Members of this set of ASNs; can be a list of ASNs or multiple as-set objects.
  • mbrs-by-ref: The Org IDs, preceded by MNT-, whose aut-num objects can be included in this set. Those aut-num objects must themselves contain this as-set in their member-of field. If this field contains “ANY,” any aut-num referring to the set (in its member-of field) will be included as a member of the set. If this field is left blank, the set is defined explicitly by the members field.

Command Example:

POST https://reg.arin.net/rest/irr/as-set?apikey=API-1234-5678-2222-3333&orgHandle=EXAMPLECORP

Payload Example:

as-set: AS-EXAMPLE-ARIZ
mnt-by: MNT-EXAMPLECORP
descr: Peers in AZ network
tech-c: EXAMPLETECH-ARIN
admin-c: EXAMPLEADMIN-ARIN
remarks: This is an example.
members: AS-PHOENIX
members: AS-MESA
members: AS-SEDONA
source: ARIN
Returns:

200 OK response and RPSL of the created object.


Viewing an as-set Object

This call gets information about an as-set object. (Note that at this time, IRR objects created in IRR-Online cannot be viewed using the REST API.)

Method: GET
URL: /rest/irr/as-set/AS-SETNAME?apikey=APIKEY
Header:

Accept: application/rpsl
Content: None
Command Example:

GET https://reg.arin.net/rest/irr/as-set/AS-EXAMPLE-ARIZ?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the object.


Modifying an as-set Object

This call modifies an as-set object. (Note that at this time, IRR objects created in IRR-Online cannot be modified using the REST API.)

Method: PUT URL: /rest/irr/as-set/AS-SETNAME?apikey=APIKEY
Header:

Accept: application/rpsl
Content-Type: application/rpsl

Content: Payload as described in Creating an as-set Object.
Command Example:

PUT https://reg.arin.net/rest/irr/as-set/AS-EXAMPLE-ARIZ?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the modified object.


Deleting an as-set Object

This call deletes an as-set object. (Note that at this time, IRR objects created in IRR-Online cannot be deleted using the REST API.)

Method: DELETE
URL: /rest/irr/as-set/AS-SETNAME?apikey=APIKEY
Header:

Accept: application/rpsl
Content: None
Command Example:

DELETE https://reg.arin.net/as-set/AS-EXAMPLE-ARIZ?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the deleted object.


route-set Objects

Creating a route-set Object

This call creates a route-set object. These objects group a list of individual IPv4 address prefixes (called members), IPv6 address prefixes (mp-members), and other objects referred to in the mbrs-by-ref field. The route-set can then be referred to in other IRR objects.

Method: POST
URL: /rest/irr/route-set?apikey=APIKEY&orgHandle=HANDLE
Header:

Content-Type: application/rpsl
Accept: application/rpsl
Content: Payload in RPSL format that contains the following:

  • route-set: A name you give to the route-set. Begins with RS- or with an AS that is managed by your organization followed by a colon and RS- (for example, AS65536:RS-ARIZ-SE-5).
  • descr: In the description, enter any information you think needs to be here. This could be your name and address, your ISP’s name, or a network name or location.
  • admin-c: Admin POC for the organization that is maintaining the object. This field is the exact POC Handle as shown in Whois for the Org ID.
  • tech-c: Tech POC for the organization that is maintaining the object. This field is the exact POC Handle as shown in Whois for the Org ID.
  • mnt-by: The prefix MNT and the Org ID of the organization that configures (maintains) the IRR object and manages the resource that is specified in the route object. It is in the format MNT-OrgID; for example, MNT-SAMPLEORG.
  • source: ARIN  Do not use any other value; all objects must have this line.
  • remarks: Any additional information the creator of the objects wants to provide (this information will also be published in the IRR database).
  • members: Members of the set; ARIN accepts IPv4 address prefixes or other route-set names.
  • mp-members: Members of the set; IPv4 and IPv6 address prefixes or other route-set names.
  • mbrs-by-ref: The Org IDs, preceded by MNT-, whose route or route6 objects should be included in this set. Those route/route6 objects must then contain this rs-set in their member-of field.

Command Example:

POST https://reg.arin.net/rest/irr/route-set?apikey=API-1234-5678-2222-3333&OrgHandle=EXAMPLECORP

Payload Example:

route-set: RS-ARIZONA-SOUTH
mnt-by: MNT-EXAMPLECORP
descr: set of Southern AZ routes
tech-c: EXAMPLETECH-ARIN
admin-c: EXAMPLEADMIN-ARIN
remarks: This is an example.
members: 192.0.2.0/24
mp-members: 2001:db8::/32
source: ARIN
Returns:

200 OK response and RPSL of the created object.


Viewing a route-set Object

This call gets information about a route-set object. (Note that at this time, IRR objects created in IRR-Online cannot be viewed using the REST API.)

Method: GET
URL: /rest/irr/route-set/RS-SETNAME?apikey=APIKEY
Header:

Accept: application/rpsl
Content: None
Command Example:

GET https://reg.arin.net/rest/irr/route-set/RS-ARIZONA-SOUTH?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the object.


Modifying a route-set Object

This call modifies a route-set object. (Note that at this time, IRR objects created in IRR-Online cannot be modified using the REST API.)

Method: PUT
URL: /rest/irr/route-set/RS-SETNAME?apikey=APIKEY
Header:

Accept: application/rpsl
Content-Type: application/rpsl

Content: Payload as described in Creating a route-set Object.
Command Example:

PUT https://reg.arin.net/rest/irr/route-set/RS-ARIZONA-SOUTH?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the modified object.


Deleting a route-set Object

This call deletes a route-set object. (Note that at this time, IRR objects created in IRR-Online cannot be deleted using the REST API.)

Method: DELETE
URL: /rest/irr/route-set/RS-SETNAME?apikey=APIKEY
Header:

Accept: application/rpsl
Content: None
Command Example:

DELETE https://reg.arin.net/route-set/RS-ARIZONA-SOUTH?apikey=API-1234-5678-2222-3333

Returns:

200 OK response and RPSL of the deleted object.


Error Codes

This list includes some of the error codes that may be returned if you send an incorrect command or payload. A message is returned with additional information on the error; the following table provides some additional information on errors that may be returned. (Tip: Use your browser’s search feature to find a specific message.)

400 Bad Request

Some of the causes of a 400 Bad Request response are provided in the following sections:

  • E_AUTHENTICATION: The API key specified was missing or invalid.
  • E_BAD_REQUEST: An aut-num object with the specified ASN already exists.
  • E_ENTITY_VALIDATION:
    • The payload entity failed to validate; see component messages for details.
    • Changing the value of the mnt-by field is not supported. The mnt-by value in the call does not match the mnt-by value of the existing record or the Org Handle of the organization that maintains the resource.
    • Prefix: Unable to create a route with this prefix. Make sure that your organization, as specified in the mnt-by field (MNT-OrgID) in your payload, manages the IP address block specified in your request.
    • Each specified tech-c must match a Tech or Routing Point of Contact (POC) associated with the Org ID (as shown in Whois) that is specified as a maintainer in the mnt-by field. One or more tech-c fields are not valid Tech POCs for the specified organization.
    • A route object with the specified prefix and origin already exists.
    • Changing the origin of a route object is not supported. You cannot modify a route or route6 object to change the ASN origination; you need to delete the object and submit a new route or route6 object with the desired new ASN.
    • Duplicate entries are not allowed. Duplicate members in the member-of attribute are not supported.
    • The ASN in the request URL path must match the ASN in the RPSL payload.
    • The specified admin-c must be the Admin POC of the Org ID specified as the maintainer in the mnt-by field. The specified admin-c does not match the Admin POC listed in Whois for the specified organization.
    • The specified prefix is off-bit. The route contains an address that is not valid with the mask (prefix length), or block size, specified (/xx). For example, 2001:db8::/20 would be off-bit, but 2001:db8::/32 would be valid.
  • E_SCHEMA_VALIDATION:
    • Something is wrong with your payload; for example, information is missing from your payload, a value is incorrect in your payload, or your payload has an extra line space. A message may be returned that provides more specific information.
    • The RPSL payload must specify source: ARIN.

Other Error Responses

  • 405 Method Not Allowed
    • E_BAD_REQUEST: Method not allowed. Ensure that the proper HTTP method has been used for this request. The wrong method (e.g., PUT, POST) is specified, or the URL contains incorrect information.
  • 406 Not Acceptable
    • E_BAD_REQUEST: No match for accept header. The Accept header must be set to the following media type: application/rpsl Make sure this header is included correctly in your call.
  • 415 Unsupported Media Type
    • E_BAD_REQUEST: Cannot consume content type. The Content-Type header for this request must be set to the following media type: application/rpsl Make sure this header is included correctly in your call if you are sending a payload.
  • 503 Service Unavailable
    • E_UNSUPPORTED_OPERATION: Operation not supported. Currently, IRR objects that were created with IRR-online can only be accessed with IRR-online. They cannot be viewed, changed, or deleted using IRR REST calls.
  • exception.rpslParse: The RPSL payload you provided cannot be parsed. The system does not understand the format of the aut-num payload that you sent. Refer to aut-num Objects for the correct payload format.
  • java.lang.IllegalStateException: Cannot validate payload with unsupported media type. You do not have the required application or content-type headers of application/rpsl in your request.
  • exception.multipleMntBy: Specify only one maintainer in the mnt-by field.
  • exception.asZeroException: The specified origin AS0 is not supported.