Saying Goodbye to an API

On 5 December 2014, we received a resource request, which would normally be an uneventful occurrence. However, this was the first time we received such a request via the API. Nearly ten years and many requests later, we have decided to terminate the Resource Requests API. This will take place on 6 January 2025 as announced on the RIPE NCC Services Working Group mailing list.

This doesn’t mean you’ll no longer be able to make use of the APIs - far from it. The RestfulAPI is still alive and kicking, but we want to explain why we decided to decommission the request part.

Numbers

To start, let’s take a look at some numbers. Following that first resource request via the API in 2014, we saw another seven that December. Then the following year, another 64. After that, as you can see, the numbers have been going up and down each year, with the high peak of 1,311 in 2021.

So far in 2024, the 69 requests received via the API have come from 17 different Local Internet Registries (LIRs).

To put the numbers in perspective, we received 4,962 resource requests over the last 12 months and of those only 100 were submitted using the API. That’s about 2%. Even at their peak in 2021, API requests only made up around 5% of all requests, and the trend has been a downwards one ever since.

Is it worth it?

The Resource Requests API is quite a "high-maintenance" item - any time a change takes place, it involves a code update as well as an update in our training material. The API is also expensive to maintain and RIPE NCC members have asked the RIPE NCC to reduce costs. Furthermore, not all resource requests are supported by the API.

A very important factor is that requests made using the API can be made by anyone, even those without a RIPE NCC Access account. Earlier this year, we made Two-Factor Authentication mandatory and we want to ensure that all requests go through this step.

Some of you will be disappointed with this decision, but please rest assured that the Registry will continue to offer its world-class support when you submit resource requests for yourselves or on behalf of your End Users. Requests, of course, can be submitted via the LIR Portal.

Many thanks to those involved in the functioning of the Resource Request API and to those who made use of it.