Skip to main content
POST
/
api
/
rdap
/
entities
/rdap/entities
curl --request POST \
  --url https://api.anysite.io/api/rdap/entities \
  --header 'Content-Type: application/json' \
  --header 'access-token: <api-key>' \
  --data '
{
  "entity": "<string>",
  "timeout": 300
}
'
[
  {
    "@type": "@rdap_entity_detail",
    "handle": "<string>",
    "roles": [],
    "status": [],
    "contact": {
      "@type": "@rdap_vcard",
      "name": "<string>",
      "org": "<string>",
      "email": "<string>",
      "phone": "<string>",
      "address": "<string>",
      "kind": "<string>"
    },
    "registrar_id": "<string>",
    "registered_at": "<string>",
    "updated_at": "<string>",
    "entities": []
  }
]

Authorizations

​
access-token
string
header
required

API token from the dashboard

Headers

​
access-token
string
required

Body

application/json
​
entity
string
required

Registry entity handle to look up

Minimum string length: 1
Examples:

"ABUSE5250-ARIN"

"ZG39-ARIN"

"RAR939-FRNIC"

​
timeout
integer
default:300

Max scrapping execution timeout (in seconds)

Required range: 20 <= x <= 1500

Response

Successful Response

​
@type
string
default:@rdap_entity_detail
​
handle
string | null
​
roles
string[]
​
status
string[]
​
contact
RdapVcard · object

Normalized contact extracted from an RDAP entity's jCard (RFC 7095).

The upstream vcardArray is a POSITIONAL array, NOT a key/value object: ["vcard", [["fn", {}, "text", "Name"], ["email", {}, "text", "a@b.c"], ...]] Each property is a 4-element array [name, params, value_type, value]. Because the format is positional (index 0 = property name, index 3 = value), mg/mgo (which navigate dict keys / treat numeric path segments as list indices) cannot address it cleanly — so the jCard walker below uses direct positional indexing with explicit length guards. This is the only place direct indexing is allowed.

​
registrar_id
string | null
​
registered_at
string | null
​
updated_at
string | null
​
entities
RdapEntity · object[]