# Profile Registries

1. **Create Registrant**

* **POST** `/api/v1/white-label-logic/registrant`

This API endpoint allows users to create a registrant.

**Request Headers**

| **Name**      | **Description**                  |
| ------------- | -------------------------------- |
| Authorization | Required: Bearer {Authorization} |

**Request Body**

```json
{
  "name": "Test-Registrant",
  "organization": "Goodcode",
  "street": "via Rime 33",
  "city": "Mendrisio",
  "postalCode": "6826",
  "country": "Switzerland",
  "phone": "+41782711212",
  "fax": "",
  "email": "goodcode@gmail.com",
  "web": "",
  "dnsSec": "",
  "walletAddress": "312317x1312321"
}
```

**Response**

**201 Created**

```json
{
    "timestamp": "2024-05-29T11:41:41.003547",
    "data": {
        "uuid": "3b39ee47-3d9a-4c42-b119-14325d518dc7",
        "name": "test-registrant-2",
        "organization": "testorg",
        "street": "testorg",
        "city": "testorg",
        "postalCode": "testorg",
        "country": "testorg",
        "phone": "testorg",
        "fax": "testorg",
        "email": "testorg@gmail.com",
        "web": "testorg",
        "dnsSec": "testorg",
        "walletAddress": "testorg"
    }
}
```

2. **Fetch Registrars**

* **GET** `/api/v1/white-label-logic/registrar`

This API endpoint allows users to fetch all registrars.

**Request Headers**

<table data-header-hidden><thead><tr><th width="176"></th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td><strong>Description</strong></td></tr><tr><td>Bearer Token</td><td>[<strong>Required</strong>] The authorization token for accessing the API.</td></tr></tbody></table>

**Response**

**200 OK**

```json
{
    "timestamp": "2024-06-18T16:18:38.656077",
    "size": 10,
    "data": [
        {
            "uuid": "81a64953-dd98-423f-85ee-cec7f36f54dd",
            "type": "REGISTRAR",
            "name": "Unstoppable Domains",
            "organization": "Unstoppable Domains Inc.",
            "street": " 8465 W Sahara Ave Ste 111",
            "city": "Las Vegas",
            "postalCode": "NV 89117",
            "country": "United States",
            "phone": "",
            "fax": "",
            "email": "support@unstoppabledomains.com",
            "web": "https://unstoppabledomains.com",
            "walletAddress": "0xDA4f3b40Ad025DF3516C345919cff348F285e507"
        },
        {
            "uuid": "135336e1-c204-41bf-98d1-252ed3d25bd2",
            "type": "REGISTRAR",
            "name": "ENS Domains",
            "organization": "ENS Domains",
            "street": "Central Region",
            "city": "Singapore",
            "country": "Singapore",
            "phone": "+1 866 757 9231",
            "email": "press@ens.domains\n",
            "web": "https://ens.domains",
            "walletAddress": "0x4Fe4e666Be5752f1FdD210F4Ab5DE2Cc26e3E0e8"
        },
        ...
    ]
}
```

3. **Fetch Profile Registry by Wallet Address**

* **GET** `/api/v1/white-label-logic/profile-registry/{walletAddress}`

This API endpoint allows to fetch a profile registry by wallet address.

**Request Headers**

<table data-header-hidden><thead><tr><th width="152"></th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td><strong>Description</strong></td></tr><tr><td>Bearer Token</td><td>[<strong>Required</strong>] The authorization token for accessing the API.</td></tr></tbody></table>

**Response**

**200 OK**

```json
{
    "timestamp": "2024-06-18T16:21:17.338821",
    "data": {
        "uuid": "94bfc7dc-...-fb287e626b74",
        "type": "REGISTRANT",
        "email": "example@freename.io",
        "walletAddress": "0x6721e82...ad2d07f"
    }
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://freename-1.gitbook.io/freename-apis/web3-white-label-apis/white-label-controller/profile-registries.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.