@hostinger/mcp 3.34.1 → 3.35.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +27 -0
- package/README.md +26 -1
- package/gemini-extension.json +1 -1
- package/package.json +1 -1
- package/server.json +2 -2
- package/skills/headless/VERSION +1 -1
- package/src/core/runtime.js +1 -1
- package/src/core/runtime.ts +1 -1
- package/src/core/tools/all.js +5 -5
- package/src/core/tools/all.ts +5 -5
- package/src/core/tools/domains.js +5 -5
- package/src/core/tools/domains.ts +5 -5
- package/src/servers/agency-hosting.js +1 -1
- package/src/servers/agency-hosting.ts +1 -1
- package/src/servers/agent-readiness.js +1 -1
- package/src/servers/agent-readiness.ts +1 -1
- package/src/servers/all.js +1 -1
- package/src/servers/all.ts +1 -1
- package/src/servers/billing.js +1 -1
- package/src/servers/billing.ts +1 -1
- package/src/servers/dns.js +1 -1
- package/src/servers/dns.ts +1 -1
- package/src/servers/domains.js +1 -1
- package/src/servers/domains.ts +1 -1
- package/src/servers/ecommerce.js +1 -1
- package/src/servers/ecommerce.ts +1 -1
- package/src/servers/gpu.js +1 -1
- package/src/servers/gpu.ts +1 -1
- package/src/servers/horizons.js +1 -1
- package/src/servers/horizons.ts +1 -1
- package/src/servers/hosting.js +1 -1
- package/src/servers/hosting.ts +1 -1
- package/src/servers/mail.js +1 -1
- package/src/servers/mail.ts +1 -1
- package/src/servers/reach.js +1 -1
- package/src/servers/reach.ts +1 -1
- package/src/servers/vps.js +1 -1
- package/src/servers/vps.ts +1 -1
- package/src/servers/wordpress.js +1 -1
- package/src/servers/wordpress.ts +1 -1
- package/types.d.ts +26 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,33 @@ Generated at release time from the diff between the previous and current
|
|
|
4
4
|
build. Tool changes are listed individually; everything else is summarised
|
|
5
5
|
by area.
|
|
6
6
|
|
|
7
|
+
## v3.35.1 — 2026-11-10
|
|
8
|
+
|
|
9
|
+
### Operations
|
|
10
|
+
|
|
11
|
+
- Changed the description of `domains_forwarding_update`
|
|
12
|
+
- Changed the description of `domains_forwarding_create`
|
|
13
|
+
|
|
14
|
+
### Also in this release
|
|
15
|
+
|
|
16
|
+
- Documentation: `README.md`
|
|
17
|
+
- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
|
|
18
|
+
- Build and packaging: `types.d.ts`
|
|
19
|
+
|
|
20
|
+
## v3.35.0 — 2026-11-10
|
|
21
|
+
|
|
22
|
+
### Operations
|
|
23
|
+
|
|
24
|
+
- Changed the description of `domains_portfolio_get`
|
|
25
|
+
- Changed the description of `domains_portfolio_list`
|
|
26
|
+
- Changed the description of `domains_portfolio_complete-setup`
|
|
27
|
+
|
|
28
|
+
### Also in this release
|
|
29
|
+
|
|
30
|
+
- Documentation: `README.md`
|
|
31
|
+
- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
|
|
32
|
+
- Build and packaging: `types.d.ts`
|
|
33
|
+
|
|
7
34
|
## v3.34.1 — 2026-11-10
|
|
8
35
|
|
|
9
36
|
### Operations
|
package/README.md
CHANGED
|
@@ -1033,6 +1033,14 @@ Use this endpoint to view current redirect configuration for domains.
|
|
|
1033
1033
|
|
|
1034
1034
|
Update domain forwarding configuration.
|
|
1035
1035
|
|
|
1036
|
+
Updating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are
|
|
1037
|
+
switched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted
|
|
1038
|
+
elsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced
|
|
1039
|
+
with records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's
|
|
1040
|
+
current nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the
|
|
1041
|
+
user before updating a forwarding on a domain that uses other nameservers. DNS changes can take some time to
|
|
1042
|
+
propagate.
|
|
1043
|
+
|
|
1036
1044
|
Use this endpoint to modify existing redirect configuration for domains.
|
|
1037
1045
|
|
|
1038
1046
|
- **Method**: `PUT`
|
|
@@ -1051,6 +1059,14 @@ Use this endpoint to remove redirect configuration from domains.
|
|
|
1051
1059
|
|
|
1052
1060
|
Create domain forwarding configuration.
|
|
1053
1061
|
|
|
1062
|
+
Creating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are
|
|
1063
|
+
switched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted
|
|
1064
|
+
elsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced
|
|
1065
|
+
with records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's
|
|
1066
|
+
current nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the
|
|
1067
|
+
user before creating a forwarding on a domain that uses other nameservers. DNS changes can take some time to
|
|
1068
|
+
propagate.
|
|
1069
|
+
|
|
1054
1070
|
Use this endpoint to set up domain redirects to other URLs.
|
|
1055
1071
|
|
|
1056
1072
|
- **Method**: `POST`
|
|
@@ -1266,6 +1282,10 @@ Use this endpoint to prepare domains for transfer to other registrars.
|
|
|
1266
1282
|
|
|
1267
1283
|
Retrieve detailed information for specified domain.
|
|
1268
1284
|
|
|
1285
|
+
A domain is found here only once it is registered. Until then, `Get domain list` shows it, and
|
|
1286
|
+
its `verification` field says what registration waits for when the domain is held for
|
|
1287
|
+
verification.
|
|
1288
|
+
|
|
1269
1289
|
Use this endpoint to view comprehensive domain configuration and status.
|
|
1270
1290
|
|
|
1271
1291
|
- **Method**: `GET`
|
|
@@ -1279,6 +1299,10 @@ A plan can include both a free domain (`type: free_domain`) and a free domain
|
|
|
1279
1299
|
transfer (`type: free_domain_transfer`). They are alternatives: claiming one
|
|
1280
1300
|
removes the other, which may still be listed for a short time after the claim.
|
|
1281
1301
|
|
|
1302
|
+
A domain held for verification before it is registered has `status: pending_verification`,
|
|
1303
|
+
and its `verification` field says what registration waits for: a manual review, an SMS code,
|
|
1304
|
+
or owner contact verification.
|
|
1305
|
+
|
|
1282
1306
|
Use this endpoint to view user's domain portfolio.
|
|
1283
1307
|
|
|
1284
1308
|
- **Method**: `GET`
|
|
@@ -1365,7 +1389,8 @@ The domain is set up with the default nameservers and with privacy protection. U
|
|
|
1365
1389
|
|
|
1366
1390
|
A successful response means the setup request was accepted, not that the domain is already
|
|
1367
1391
|
registered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`
|
|
1368
|
-
only once it is registered.
|
|
1392
|
+
only once it is registered. When the domain is held for verification, its `verification` field
|
|
1393
|
+
in `Get domain list` says what registration waits for.
|
|
1369
1394
|
|
|
1370
1395
|
Use this endpoint to finish registering a domain that is awaiting setup on your account.
|
|
1371
1396
|
|
package/gemini-extension.json
CHANGED
package/package.json
CHANGED
package/server.json
CHANGED
|
@@ -17,12 +17,12 @@
|
|
|
17
17
|
"url": "https://github.com/hostinger/api-mcp-server",
|
|
18
18
|
"source": "github"
|
|
19
19
|
},
|
|
20
|
-
"version": "3.
|
|
20
|
+
"version": "3.35.1",
|
|
21
21
|
"packages": [
|
|
22
22
|
{
|
|
23
23
|
"registryType": "npm",
|
|
24
24
|
"identifier": "@hostinger/mcp",
|
|
25
|
-
"version": "3.
|
|
25
|
+
"version": "3.35.1",
|
|
26
26
|
"transport": {
|
|
27
27
|
"type": "stdio"
|
|
28
28
|
},
|
package/skills/headless/VERSION
CHANGED
package/src/core/runtime.js
CHANGED
|
@@ -62,7 +62,7 @@ const GetSkillRequestSchema = z.object({
|
|
|
62
62
|
|
|
63
63
|
/**
|
|
64
64
|
* MCP Server for Hostinger API
|
|
65
|
-
* Generated from OpenAPI spec version 2.
|
|
65
|
+
* Generated from OpenAPI spec version 2.12.1
|
|
66
66
|
*/
|
|
67
67
|
class MCPServer {
|
|
68
68
|
constructor({ name, version, tools, instructions, skills = [] }) {
|
package/src/core/runtime.ts
CHANGED
|
@@ -94,7 +94,7 @@ interface Skill { uri: string; frontmatter: Record<string, unknown>; resources:
|
|
|
94
94
|
|
|
95
95
|
/**
|
|
96
96
|
* MCP Server for Hostinger API
|
|
97
|
-
* Generated from OpenAPI spec version 2.
|
|
97
|
+
* Generated from OpenAPI spec version 2.12.1
|
|
98
98
|
*/
|
|
99
99
|
class MCPServer {
|
|
100
100
|
private readonly name: string;
|
package/src/core/tools/all.js
CHANGED
|
@@ -3554,7 +3554,7 @@ export default [
|
|
|
3554
3554
|
"destructiveHint": true,
|
|
3555
3555
|
"idempotentHint": true
|
|
3556
3556
|
},
|
|
3557
|
-
"description": "Update domain forwarding configuration.\n\nUse this endpoint to modify existing redirect configuration for domains.",
|
|
3557
|
+
"description": "Update domain forwarding configuration.\n\nUpdating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are\nswitched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted\nelsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced\nwith records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's\ncurrent nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the\nuser before updating a forwarding on a domain that uses other nameservers. DNS changes can take some time to\npropagate.\n\nUse this endpoint to modify existing redirect configuration for domains.",
|
|
3558
3558
|
"method": "PUT",
|
|
3559
3559
|
"path": "/api/domains/v1/forwarding/{domain}",
|
|
3560
3560
|
"inputSchema": {
|
|
@@ -3629,7 +3629,7 @@ export default [
|
|
|
3629
3629
|
"readOnlyHint": false,
|
|
3630
3630
|
"destructiveHint": false
|
|
3631
3631
|
},
|
|
3632
|
-
"description": "Create domain forwarding configuration.\n\nUse this endpoint to set up domain redirects to other URLs.",
|
|
3632
|
+
"description": "Create domain forwarding configuration.\n\nCreating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are\nswitched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted\nelsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced\nwith records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's\ncurrent nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the\nuser before creating a forwarding on a domain that uses other nameservers. DNS changes can take some time to\npropagate.\n\nUse this endpoint to set up domain redirects to other URLs.",
|
|
3633
3633
|
"method": "POST",
|
|
3634
3634
|
"path": "/api/domains/v1/forwarding",
|
|
3635
3635
|
"inputSchema": {
|
|
@@ -4150,7 +4150,7 @@ export default [
|
|
|
4150
4150
|
"readOnlyHint": true,
|
|
4151
4151
|
"destructiveHint": false
|
|
4152
4152
|
},
|
|
4153
|
-
"description": "Retrieve detailed information for specified domain.\n\nUse this endpoint to view comprehensive domain configuration and status.",
|
|
4153
|
+
"description": "Retrieve detailed information for specified domain.\n\nA domain is found here only once it is registered. Until then, `Get domain list` shows it, and\nits `verification` field says what registration waits for when the domain is held for\nverification.\n\nUse this endpoint to view comprehensive domain configuration and status.",
|
|
4154
4154
|
"method": "GET",
|
|
4155
4155
|
"path": "/api/domains/v1/portfolio/{domain}",
|
|
4156
4156
|
"inputSchema": {
|
|
@@ -4180,7 +4180,7 @@ export default [
|
|
|
4180
4180
|
"readOnlyHint": true,
|
|
4181
4181
|
"destructiveHint": false
|
|
4182
4182
|
},
|
|
4183
|
-
"description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nUse this endpoint to view user's domain portfolio.",
|
|
4183
|
+
"description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nA domain held for verification before it is registered has `status: pending_verification`,\nand its `verification` field says what registration waits for: a manual review, an SMS code,\nor owner contact verification.\n\nUse this endpoint to view user's domain portfolio.",
|
|
4184
4184
|
"method": "GET",
|
|
4185
4185
|
"path": "/api/domains/v1/portfolio",
|
|
4186
4186
|
"inputSchema": {
|
|
@@ -4369,7 +4369,7 @@ export default [
|
|
|
4369
4369
|
"readOnlyHint": false,
|
|
4370
4370
|
"destructiveHint": false
|
|
4371
4371
|
},
|
|
4372
|
-
"description": "Register a domain you have already paid for but which has not been set up yet.\n\nUse this endpoint when an order completed without registering the domain, for example when\n`Purchase new domain` returned `202 Accepted` and the domain was added to your account without\nbeing registered, or when an earlier setup attempt failed. No new order is placed and no payment\nis taken: the subscription you already own is used, for the period you already paid for.\n\nA domain is left awaiting setup when the details needed to register it were missing or invalid\nas the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.\nComplete the missing information, then call this endpoint. If the order itself has not completed\nyet, the domain is not on your account, wait until it appears in `Get domain list`.\n\nIf `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four\nroles. The profile must exist and be complete for the TLD, an incomplete profile is the most\ncommon reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.\n\nSome TLDs require `additional_details`. These are validated before setup, so a missing or\ninvalid value is rejected without any registration being attempted.\n\nThe domain is set up with the default nameservers and with privacy protection. Use\n`Update domain nameservers` and `Disable privacy protection` afterwards to change either.\n\nA successful response means the setup request was accepted, not that the domain is already\nregistered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`\nonly once it is registered.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
|
|
4372
|
+
"description": "Register a domain you have already paid for but which has not been set up yet.\n\nUse this endpoint when an order completed without registering the domain, for example when\n`Purchase new domain` returned `202 Accepted` and the domain was added to your account without\nbeing registered, or when an earlier setup attempt failed. No new order is placed and no payment\nis taken: the subscription you already own is used, for the period you already paid for.\n\nA domain is left awaiting setup when the details needed to register it were missing or invalid\nas the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.\nComplete the missing information, then call this endpoint. If the order itself has not completed\nyet, the domain is not on your account, wait until it appears in `Get domain list`.\n\nIf `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four\nroles. The profile must exist and be complete for the TLD, an incomplete profile is the most\ncommon reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.\n\nSome TLDs require `additional_details`. These are validated before setup, so a missing or\ninvalid value is rejected without any registration being attempted.\n\nThe domain is set up with the default nameservers and with privacy protection. Use\n`Update domain nameservers` and `Disable privacy protection` afterwards to change either.\n\nA successful response means the setup request was accepted, not that the domain is already\nregistered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`\nonly once it is registered. When the domain is held for verification, its `verification` field\nin `Get domain list` says what registration waits for.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
|
|
4373
4373
|
"method": "POST",
|
|
4374
4374
|
"path": "/api/domains/v1/portfolio/{domain}/setup",
|
|
4375
4375
|
"inputSchema": {
|
package/src/core/tools/all.ts
CHANGED
|
@@ -3571,7 +3571,7 @@ const tools: OpenApiTool[] = [
|
|
|
3571
3571
|
"destructiveHint": true,
|
|
3572
3572
|
"idempotentHint": true
|
|
3573
3573
|
},
|
|
3574
|
-
"description": "Update domain forwarding configuration.\n\nUse this endpoint to modify existing redirect configuration for domains.",
|
|
3574
|
+
"description": "Update domain forwarding configuration.\n\nUpdating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are\nswitched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted\nelsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced\nwith records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's\ncurrent nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the\nuser before updating a forwarding on a domain that uses other nameservers. DNS changes can take some time to\npropagate.\n\nUse this endpoint to modify existing redirect configuration for domains.",
|
|
3575
3575
|
"method": "PUT",
|
|
3576
3576
|
"path": "/api/domains/v1/forwarding/{domain}",
|
|
3577
3577
|
"inputSchema": {
|
|
@@ -3646,7 +3646,7 @@ const tools: OpenApiTool[] = [
|
|
|
3646
3646
|
"readOnlyHint": false,
|
|
3647
3647
|
"destructiveHint": false
|
|
3648
3648
|
},
|
|
3649
|
-
"description": "Create domain forwarding configuration.\n\nUse this endpoint to set up domain redirects to other URLs.",
|
|
3649
|
+
"description": "Create domain forwarding configuration.\n\nCreating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are\nswitched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted\nelsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced\nwith records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's\ncurrent nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the\nuser before creating a forwarding on a domain that uses other nameservers. DNS changes can take some time to\npropagate.\n\nUse this endpoint to set up domain redirects to other URLs.",
|
|
3650
3650
|
"method": "POST",
|
|
3651
3651
|
"path": "/api/domains/v1/forwarding",
|
|
3652
3652
|
"inputSchema": {
|
|
@@ -4167,7 +4167,7 @@ const tools: OpenApiTool[] = [
|
|
|
4167
4167
|
"readOnlyHint": true,
|
|
4168
4168
|
"destructiveHint": false
|
|
4169
4169
|
},
|
|
4170
|
-
"description": "Retrieve detailed information for specified domain.\n\nUse this endpoint to view comprehensive domain configuration and status.",
|
|
4170
|
+
"description": "Retrieve detailed information for specified domain.\n\nA domain is found here only once it is registered. Until then, `Get domain list` shows it, and\nits `verification` field says what registration waits for when the domain is held for\nverification.\n\nUse this endpoint to view comprehensive domain configuration and status.",
|
|
4171
4171
|
"method": "GET",
|
|
4172
4172
|
"path": "/api/domains/v1/portfolio/{domain}",
|
|
4173
4173
|
"inputSchema": {
|
|
@@ -4197,7 +4197,7 @@ const tools: OpenApiTool[] = [
|
|
|
4197
4197
|
"readOnlyHint": true,
|
|
4198
4198
|
"destructiveHint": false
|
|
4199
4199
|
},
|
|
4200
|
-
"description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nUse this endpoint to view user's domain portfolio.",
|
|
4200
|
+
"description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nA domain held for verification before it is registered has `status: pending_verification`,\nand its `verification` field says what registration waits for: a manual review, an SMS code,\nor owner contact verification.\n\nUse this endpoint to view user's domain portfolio.",
|
|
4201
4201
|
"method": "GET",
|
|
4202
4202
|
"path": "/api/domains/v1/portfolio",
|
|
4203
4203
|
"inputSchema": {
|
|
@@ -4386,7 +4386,7 @@ const tools: OpenApiTool[] = [
|
|
|
4386
4386
|
"readOnlyHint": false,
|
|
4387
4387
|
"destructiveHint": false
|
|
4388
4388
|
},
|
|
4389
|
-
"description": "Register a domain you have already paid for but which has not been set up yet.\n\nUse this endpoint when an order completed without registering the domain, for example when\n`Purchase new domain` returned `202 Accepted` and the domain was added to your account without\nbeing registered, or when an earlier setup attempt failed. No new order is placed and no payment\nis taken: the subscription you already own is used, for the period you already paid for.\n\nA domain is left awaiting setup when the details needed to register it were missing or invalid\nas the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.\nComplete the missing information, then call this endpoint. If the order itself has not completed\nyet, the domain is not on your account, wait until it appears in `Get domain list`.\n\nIf `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four\nroles. The profile must exist and be complete for the TLD, an incomplete profile is the most\ncommon reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.\n\nSome TLDs require `additional_details`. These are validated before setup, so a missing or\ninvalid value is rejected without any registration being attempted.\n\nThe domain is set up with the default nameservers and with privacy protection. Use\n`Update domain nameservers` and `Disable privacy protection` afterwards to change either.\n\nA successful response means the setup request was accepted, not that the domain is already\nregistered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`\nonly once it is registered.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
|
|
4389
|
+
"description": "Register a domain you have already paid for but which has not been set up yet.\n\nUse this endpoint when an order completed without registering the domain, for example when\n`Purchase new domain` returned `202 Accepted` and the domain was added to your account without\nbeing registered, or when an earlier setup attempt failed. No new order is placed and no payment\nis taken: the subscription you already own is used, for the period you already paid for.\n\nA domain is left awaiting setup when the details needed to register it were missing or invalid\nas the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.\nComplete the missing information, then call this endpoint. If the order itself has not completed\nyet, the domain is not on your account, wait until it appears in `Get domain list`.\n\nIf `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four\nroles. The profile must exist and be complete for the TLD, an incomplete profile is the most\ncommon reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.\n\nSome TLDs require `additional_details`. These are validated before setup, so a missing or\ninvalid value is rejected without any registration being attempted.\n\nThe domain is set up with the default nameservers and with privacy protection. Use\n`Update domain nameservers` and `Disable privacy protection` afterwards to change either.\n\nA successful response means the setup request was accepted, not that the domain is already\nregistered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`\nonly once it is registered. When the domain is held for verification, its `verification` field\nin `Get domain list` says what registration waits for.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
|
|
4390
4390
|
"method": "POST",
|
|
4391
4391
|
"path": "/api/domains/v1/portfolio/{domain}/setup",
|
|
4392
4392
|
"inputSchema": {
|
|
@@ -226,7 +226,7 @@ export default [
|
|
|
226
226
|
"destructiveHint": true,
|
|
227
227
|
"idempotentHint": true
|
|
228
228
|
},
|
|
229
|
-
"description": "Update domain forwarding configuration.\n\nUse this endpoint to modify existing redirect configuration for domains.",
|
|
229
|
+
"description": "Update domain forwarding configuration.\n\nUpdating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are\nswitched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted\nelsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced\nwith records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's\ncurrent nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the\nuser before updating a forwarding on a domain that uses other nameservers. DNS changes can take some time to\npropagate.\n\nUse this endpoint to modify existing redirect configuration for domains.",
|
|
230
230
|
"method": "PUT",
|
|
231
231
|
"path": "/api/domains/v1/forwarding/{domain}",
|
|
232
232
|
"inputSchema": {
|
|
@@ -301,7 +301,7 @@ export default [
|
|
|
301
301
|
"readOnlyHint": false,
|
|
302
302
|
"destructiveHint": false
|
|
303
303
|
},
|
|
304
|
-
"description": "Create domain forwarding configuration.\n\nUse this endpoint to set up domain redirects to other URLs.",
|
|
304
|
+
"description": "Create domain forwarding configuration.\n\nCreating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are\nswitched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted\nelsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced\nwith records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's\ncurrent nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the\nuser before creating a forwarding on a domain that uses other nameservers. DNS changes can take some time to\npropagate.\n\nUse this endpoint to set up domain redirects to other URLs.",
|
|
305
305
|
"method": "POST",
|
|
306
306
|
"path": "/api/domains/v1/forwarding",
|
|
307
307
|
"inputSchema": {
|
|
@@ -822,7 +822,7 @@ export default [
|
|
|
822
822
|
"readOnlyHint": true,
|
|
823
823
|
"destructiveHint": false
|
|
824
824
|
},
|
|
825
|
-
"description": "Retrieve detailed information for specified domain.\n\nUse this endpoint to view comprehensive domain configuration and status.",
|
|
825
|
+
"description": "Retrieve detailed information for specified domain.\n\nA domain is found here only once it is registered. Until then, `Get domain list` shows it, and\nits `verification` field says what registration waits for when the domain is held for\nverification.\n\nUse this endpoint to view comprehensive domain configuration and status.",
|
|
826
826
|
"method": "GET",
|
|
827
827
|
"path": "/api/domains/v1/portfolio/{domain}",
|
|
828
828
|
"inputSchema": {
|
|
@@ -852,7 +852,7 @@ export default [
|
|
|
852
852
|
"readOnlyHint": true,
|
|
853
853
|
"destructiveHint": false
|
|
854
854
|
},
|
|
855
|
-
"description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nUse this endpoint to view user's domain portfolio.",
|
|
855
|
+
"description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nA domain held for verification before it is registered has `status: pending_verification`,\nand its `verification` field says what registration waits for: a manual review, an SMS code,\nor owner contact verification.\n\nUse this endpoint to view user's domain portfolio.",
|
|
856
856
|
"method": "GET",
|
|
857
857
|
"path": "/api/domains/v1/portfolio",
|
|
858
858
|
"inputSchema": {
|
|
@@ -1041,7 +1041,7 @@ export default [
|
|
|
1041
1041
|
"readOnlyHint": false,
|
|
1042
1042
|
"destructiveHint": false
|
|
1043
1043
|
},
|
|
1044
|
-
"description": "Register a domain you have already paid for but which has not been set up yet.\n\nUse this endpoint when an order completed without registering the domain, for example when\n`Purchase new domain` returned `202 Accepted` and the domain was added to your account without\nbeing registered, or when an earlier setup attempt failed. No new order is placed and no payment\nis taken: the subscription you already own is used, for the period you already paid for.\n\nA domain is left awaiting setup when the details needed to register it were missing or invalid\nas the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.\nComplete the missing information, then call this endpoint. If the order itself has not completed\nyet, the domain is not on your account, wait until it appears in `Get domain list`.\n\nIf `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four\nroles. The profile must exist and be complete for the TLD, an incomplete profile is the most\ncommon reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.\n\nSome TLDs require `additional_details`. These are validated before setup, so a missing or\ninvalid value is rejected without any registration being attempted.\n\nThe domain is set up with the default nameservers and with privacy protection. Use\n`Update domain nameservers` and `Disable privacy protection` afterwards to change either.\n\nA successful response means the setup request was accepted, not that the domain is already\nregistered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`\nonly once it is registered.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
|
|
1044
|
+
"description": "Register a domain you have already paid for but which has not been set up yet.\n\nUse this endpoint when an order completed without registering the domain, for example when\n`Purchase new domain` returned `202 Accepted` and the domain was added to your account without\nbeing registered, or when an earlier setup attempt failed. No new order is placed and no payment\nis taken: the subscription you already own is used, for the period you already paid for.\n\nA domain is left awaiting setup when the details needed to register it were missing or invalid\nas the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.\nComplete the missing information, then call this endpoint. If the order itself has not completed\nyet, the domain is not on your account, wait until it appears in `Get domain list`.\n\nIf `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four\nroles. The profile must exist and be complete for the TLD, an incomplete profile is the most\ncommon reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.\n\nSome TLDs require `additional_details`. These are validated before setup, so a missing or\ninvalid value is rejected without any registration being attempted.\n\nThe domain is set up with the default nameservers and with privacy protection. Use\n`Update domain nameservers` and `Disable privacy protection` afterwards to change either.\n\nA successful response means the setup request was accepted, not that the domain is already\nregistered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`\nonly once it is registered. When the domain is held for verification, its `verification` field\nin `Get domain list` says what registration waits for.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
|
|
1045
1045
|
"method": "POST",
|
|
1046
1046
|
"path": "/api/domains/v1/portfolio/{domain}/setup",
|
|
1047
1047
|
"inputSchema": {
|
|
@@ -243,7 +243,7 @@ const tools: OpenApiTool[] = [
|
|
|
243
243
|
"destructiveHint": true,
|
|
244
244
|
"idempotentHint": true
|
|
245
245
|
},
|
|
246
|
-
"description": "Update domain forwarding configuration.\n\nUse this endpoint to modify existing redirect configuration for domains.",
|
|
246
|
+
"description": "Update domain forwarding configuration.\n\nUpdating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are\nswitched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted\nelsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced\nwith records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's\ncurrent nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the\nuser before updating a forwarding on a domain that uses other nameservers. DNS changes can take some time to\npropagate.\n\nUse this endpoint to modify existing redirect configuration for domains.",
|
|
247
247
|
"method": "PUT",
|
|
248
248
|
"path": "/api/domains/v1/forwarding/{domain}",
|
|
249
249
|
"inputSchema": {
|
|
@@ -318,7 +318,7 @@ const tools: OpenApiTool[] = [
|
|
|
318
318
|
"readOnlyHint": false,
|
|
319
319
|
"destructiveHint": false
|
|
320
320
|
},
|
|
321
|
-
"description": "Create domain forwarding configuration.\n\nUse this endpoint to set up domain redirects to other URLs.",
|
|
321
|
+
"description": "Create domain forwarding configuration.\n\nCreating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are\nswitched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted\nelsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced\nwith records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's\ncurrent nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the\nuser before creating a forwarding on a domain that uses other nameservers. DNS changes can take some time to\npropagate.\n\nUse this endpoint to set up domain redirects to other URLs.",
|
|
322
322
|
"method": "POST",
|
|
323
323
|
"path": "/api/domains/v1/forwarding",
|
|
324
324
|
"inputSchema": {
|
|
@@ -839,7 +839,7 @@ const tools: OpenApiTool[] = [
|
|
|
839
839
|
"readOnlyHint": true,
|
|
840
840
|
"destructiveHint": false
|
|
841
841
|
},
|
|
842
|
-
"description": "Retrieve detailed information for specified domain.\n\nUse this endpoint to view comprehensive domain configuration and status.",
|
|
842
|
+
"description": "Retrieve detailed information for specified domain.\n\nA domain is found here only once it is registered. Until then, `Get domain list` shows it, and\nits `verification` field says what registration waits for when the domain is held for\nverification.\n\nUse this endpoint to view comprehensive domain configuration and status.",
|
|
843
843
|
"method": "GET",
|
|
844
844
|
"path": "/api/domains/v1/portfolio/{domain}",
|
|
845
845
|
"inputSchema": {
|
|
@@ -869,7 +869,7 @@ const tools: OpenApiTool[] = [
|
|
|
869
869
|
"readOnlyHint": true,
|
|
870
870
|
"destructiveHint": false
|
|
871
871
|
},
|
|
872
|
-
"description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nUse this endpoint to view user's domain portfolio.",
|
|
872
|
+
"description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nA domain held for verification before it is registered has `status: pending_verification`,\nand its `verification` field says what registration waits for: a manual review, an SMS code,\nor owner contact verification.\n\nUse this endpoint to view user's domain portfolio.",
|
|
873
873
|
"method": "GET",
|
|
874
874
|
"path": "/api/domains/v1/portfolio",
|
|
875
875
|
"inputSchema": {
|
|
@@ -1058,7 +1058,7 @@ const tools: OpenApiTool[] = [
|
|
|
1058
1058
|
"readOnlyHint": false,
|
|
1059
1059
|
"destructiveHint": false
|
|
1060
1060
|
},
|
|
1061
|
-
"description": "Register a domain you have already paid for but which has not been set up yet.\n\nUse this endpoint when an order completed without registering the domain, for example when\n`Purchase new domain` returned `202 Accepted` and the domain was added to your account without\nbeing registered, or when an earlier setup attempt failed. No new order is placed and no payment\nis taken: the subscription you already own is used, for the period you already paid for.\n\nA domain is left awaiting setup when the details needed to register it were missing or invalid\nas the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.\nComplete the missing information, then call this endpoint. If the order itself has not completed\nyet, the domain is not on your account, wait until it appears in `Get domain list`.\n\nIf `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four\nroles. The profile must exist and be complete for the TLD, an incomplete profile is the most\ncommon reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.\n\nSome TLDs require `additional_details`. These are validated before setup, so a missing or\ninvalid value is rejected without any registration being attempted.\n\nThe domain is set up with the default nameservers and with privacy protection. Use\n`Update domain nameservers` and `Disable privacy protection` afterwards to change either.\n\nA successful response means the setup request was accepted, not that the domain is already\nregistered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`\nonly once it is registered.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
|
|
1061
|
+
"description": "Register a domain you have already paid for but which has not been set up yet.\n\nUse this endpoint when an order completed without registering the domain, for example when\n`Purchase new domain` returned `202 Accepted` and the domain was added to your account without\nbeing registered, or when an earlier setup attempt failed. No new order is placed and no payment\nis taken: the subscription you already own is used, for the period you already paid for.\n\nA domain is left awaiting setup when the details needed to register it were missing or invalid\nas the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.\nComplete the missing information, then call this endpoint. If the order itself has not completed\nyet, the domain is not on your account, wait until it appears in `Get domain list`.\n\nIf `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four\nroles. The profile must exist and be complete for the TLD, an incomplete profile is the most\ncommon reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.\n\nSome TLDs require `additional_details`. These are validated before setup, so a missing or\ninvalid value is rejected without any registration being attempted.\n\nThe domain is set up with the default nameservers and with privacy protection. Use\n`Update domain nameservers` and `Disable privacy protection` afterwards to change either.\n\nA successful response means the setup request was accepted, not that the domain is already\nregistered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`\nonly once it is registered. When the domain is held for verification, its `verification` field\nin `Get domain list` says what registration waits for.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
|
|
1062
1062
|
"method": "POST",
|
|
1063
1063
|
"path": "/api/domains/v1/portfolio/{domain}/setup",
|
|
1064
1064
|
"inputSchema": {
|
|
@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
|
|
|
4
4
|
import tools from '../core/tools/agency-hosting.js';
|
|
5
5
|
import instructions from '../core/instructions.agency-hosting.js';
|
|
6
6
|
|
|
7
|
-
startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.
|
|
7
|
+
startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.35.1', tools, instructions });
|
|
@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
|
|
|
4
4
|
import tools from '../core/tools/agency-hosting.js';
|
|
5
5
|
import instructions from '../core/instructions.agency-hosting.js';
|
|
6
6
|
|
|
7
|
-
startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.
|
|
7
|
+
startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.35.1', tools, instructions });
|
|
@@ -3,4 +3,4 @@
|
|
|
3
3
|
import { startServer } from '../core/runtime.js';
|
|
4
4
|
import tools from '../core/tools/agent-readiness.js';
|
|
5
5
|
|
|
6
|
-
startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.
|
|
6
|
+
startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.35.1', tools });
|
|
@@ -3,4 +3,4 @@
|
|
|
3
3
|
import { startServer } from '../core/runtime.js';
|
|
4
4
|
import tools from '../core/tools/agent-readiness.js';
|
|
5
5
|
|
|
6
|
-
startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.
|
|
6
|
+
startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.35.1', tools });
|
package/src/servers/all.js
CHANGED
|
@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
|
|
|
5
5
|
import instructions from '../core/instructions.js';
|
|
6
6
|
import skills from '../core/skills.js';
|
|
7
7
|
|
|
8
|
-
startServer({ name: 'hostinger-api-mcp', version: '3.
|
|
8
|
+
startServer({ name: 'hostinger-api-mcp', version: '3.35.1', tools, instructions, skills });
|
package/src/servers/all.ts
CHANGED
|
@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
|
|
|
5
5
|
import instructions from '../core/instructions.js';
|
|
6
6
|
import skills from '../core/skills.js';
|
|
7
7
|
|
|
8
|
-
startServer({ name: 'hostinger-api-mcp', version: '3.
|
|
8
|
+
startServer({ name: 'hostinger-api-mcp', version: '3.35.1', tools, instructions, skills });
|
package/src/servers/billing.js
CHANGED
package/src/servers/billing.ts
CHANGED
package/src/servers/dns.js
CHANGED
package/src/servers/dns.ts
CHANGED
package/src/servers/domains.js
CHANGED
package/src/servers/domains.ts
CHANGED
package/src/servers/ecommerce.js
CHANGED
package/src/servers/ecommerce.ts
CHANGED
package/src/servers/gpu.js
CHANGED
package/src/servers/gpu.ts
CHANGED
package/src/servers/horizons.js
CHANGED
package/src/servers/horizons.ts
CHANGED
package/src/servers/hosting.js
CHANGED
|
@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
|
|
|
4
4
|
import tools from '../core/tools/hosting.js';
|
|
5
5
|
import instructions from '../core/instructions.js';
|
|
6
6
|
|
|
7
|
-
startServer({ name: 'hostinger-hosting-mcp', version: '3.
|
|
7
|
+
startServer({ name: 'hostinger-hosting-mcp', version: '3.35.1', tools, instructions });
|
package/src/servers/hosting.ts
CHANGED
|
@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
|
|
|
4
4
|
import tools from '../core/tools/hosting.js';
|
|
5
5
|
import instructions from '../core/instructions.js';
|
|
6
6
|
|
|
7
|
-
startServer({ name: 'hostinger-hosting-mcp', version: '3.
|
|
7
|
+
startServer({ name: 'hostinger-hosting-mcp', version: '3.35.1', tools, instructions });
|
package/src/servers/mail.js
CHANGED
package/src/servers/mail.ts
CHANGED
package/src/servers/reach.js
CHANGED
package/src/servers/reach.ts
CHANGED
package/src/servers/vps.js
CHANGED
package/src/servers/vps.ts
CHANGED
package/src/servers/wordpress.js
CHANGED
package/src/servers/wordpress.ts
CHANGED
package/types.d.ts
CHANGED
|
@@ -1886,6 +1886,14 @@ Use this endpoint to view current redirect configuration for domains.
|
|
|
1886
1886
|
/**
|
|
1887
1887
|
* Update domain forwarding configuration.
|
|
1888
1888
|
|
|
1889
|
+
Updating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are
|
|
1890
|
+
switched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted
|
|
1891
|
+
elsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced
|
|
1892
|
+
with records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's
|
|
1893
|
+
current nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the
|
|
1894
|
+
user before updating a forwarding on a domain that uses other nameservers. DNS changes can take some time to
|
|
1895
|
+
propagate.
|
|
1896
|
+
|
|
1889
1897
|
Use this endpoint to modify existing redirect configuration for domains.
|
|
1890
1898
|
*/
|
|
1891
1899
|
"domains_forwarding_update": {
|
|
@@ -1924,6 +1932,14 @@ Use this endpoint to remove redirect configuration from domains.
|
|
|
1924
1932
|
/**
|
|
1925
1933
|
* Create domain forwarding configuration.
|
|
1926
1934
|
|
|
1935
|
+
Creating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are
|
|
1936
|
+
switched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted
|
|
1937
|
+
elsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced
|
|
1938
|
+
with records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's
|
|
1939
|
+
current nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the
|
|
1940
|
+
user before creating a forwarding on a domain that uses other nameservers. DNS changes can take some time to
|
|
1941
|
+
propagate.
|
|
1942
|
+
|
|
1927
1943
|
Use this endpoint to set up domain redirects to other URLs.
|
|
1928
1944
|
*/
|
|
1929
1945
|
"domains_forwarding_create": {
|
|
@@ -2251,6 +2267,10 @@ Use this endpoint to prepare domains for transfer to other registrars.
|
|
|
2251
2267
|
/**
|
|
2252
2268
|
* Retrieve detailed information for specified domain.
|
|
2253
2269
|
|
|
2270
|
+
A domain is found here only once it is registered. Until then, `Get domain list` shows it, and
|
|
2271
|
+
its `verification` field says what registration waits for when the domain is held for
|
|
2272
|
+
verification.
|
|
2273
|
+
|
|
2254
2274
|
Use this endpoint to view comprehensive domain configuration and status.
|
|
2255
2275
|
*/
|
|
2256
2276
|
"domains_portfolio_get": {
|
|
@@ -2270,6 +2290,10 @@ A plan can include both a free domain (`type: free_domain`) and a free domain
|
|
|
2270
2290
|
transfer (`type: free_domain_transfer`). They are alternatives: claiming one
|
|
2271
2291
|
removes the other, which may still be listed for a short time after the claim.
|
|
2272
2292
|
|
|
2293
|
+
A domain held for verification before it is registered has `status: pending_verification`,
|
|
2294
|
+
and its `verification` field says what registration waits for: a manual review, an SMS code,
|
|
2295
|
+
or owner contact verification.
|
|
2296
|
+
|
|
2273
2297
|
Use this endpoint to view user's domain portfolio.
|
|
2274
2298
|
*/
|
|
2275
2299
|
"domains_portfolio_list": {
|
|
@@ -2403,7 +2427,8 @@ The domain is set up with the default nameservers and with privacy protection. U
|
|
|
2403
2427
|
|
|
2404
2428
|
A successful response means the setup request was accepted, not that the domain is already
|
|
2405
2429
|
registered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`
|
|
2406
|
-
only once it is registered.
|
|
2430
|
+
only once it is registered. When the domain is held for verification, its `verification` field
|
|
2431
|
+
in `Get domain list` says what registration waits for.
|
|
2407
2432
|
|
|
2408
2433
|
Use this endpoint to finish registering a domain that is awaiting setup on your account.
|
|
2409
2434
|
*/
|