RPKI validity of an ASN's registry route objects

GET

/api/v1/network/asn/{asn}/rpki

Last modified:2026-07-19 17:02:27

Maintainer:Not configured

OperationId:network_asn_asn_rpki

The ASN's RIPE Database registry route / route6 objects (inverse origin), each annotated with its RPKI Route Origin Validation verdict (valid / invalid / unknown), plus a summary. NOTE: the RIPE Database 'roa-check' search parameter is a no-op over the JSON REST API (verified live - it adds no annotation to the returned objects), so the verdict is computed per route from RPKI validation (prefix + origin). Complements the single-prefix /prefix/{cidr}/rpki with the AS-wide registry view. Upstream registry: 'global' (all RIRs via GRS, default) | ripe | ripe-nonauth | -grs.

Request

Authorization

API Key

Add parameter in header

x-api-key

Example:

x-api-key: ********************

Path Params

Query Params

Header Params

Request Code Samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

curl --location 'https://sugra.ai/api/v1/network/asn/3333/rpki?source=global&limit=undefined' \
--header 'x-api-key: <api-key>'

Responses

🟢200OK

application/json

Successful Response

Bodyapplication/json

Example

null

🟠401Unauthorized

🟠422Parameter Error

🟠429

🔴503Service Unavailable

Modified at 2026-07-19 17:02:27

Operator self-published geolocation for an IP/prefix (RIPE DB geoloc/geofeed)

Batch IP lookup (max 100)