@hostinger/mcp 3.38.3 → 3.39.0

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.
Files changed (43) hide show
  1. package/CHANGELOG.md +25 -0
  2. package/README.md +126 -9
  3. package/gemini-extension.json +1 -1
  4. package/package.json +1 -1
  5. package/server.json +2 -2
  6. package/skills/headless/VERSION +3 -3
  7. package/src/core/runtime.js +1 -1
  8. package/src/core/runtime.ts +1 -1
  9. package/src/core/tools/all.js +192 -4
  10. package/src/core/tools/all.ts +192 -4
  11. package/src/core/tools/hosting.js +190 -2
  12. package/src/core/tools/hosting.ts +190 -2
  13. package/src/core/tools/wordpress.js +2 -2
  14. package/src/core/tools/wordpress.ts +2 -2
  15. package/src/servers/agency-hosting.js +1 -1
  16. package/src/servers/agency-hosting.ts +1 -1
  17. package/src/servers/agent-readiness.js +1 -1
  18. package/src/servers/agent-readiness.ts +1 -1
  19. package/src/servers/all.js +1 -1
  20. package/src/servers/all.ts +1 -1
  21. package/src/servers/billing.js +1 -1
  22. package/src/servers/billing.ts +1 -1
  23. package/src/servers/dns.js +1 -1
  24. package/src/servers/dns.ts +1 -1
  25. package/src/servers/domains.js +1 -1
  26. package/src/servers/domains.ts +1 -1
  27. package/src/servers/ecommerce.js +1 -1
  28. package/src/servers/ecommerce.ts +1 -1
  29. package/src/servers/gpu.js +1 -1
  30. package/src/servers/gpu.ts +1 -1
  31. package/src/servers/horizons.js +1 -1
  32. package/src/servers/horizons.ts +1 -1
  33. package/src/servers/hosting.js +1 -1
  34. package/src/servers/hosting.ts +1 -1
  35. package/src/servers/mail.js +1 -1
  36. package/src/servers/mail.ts +1 -1
  37. package/src/servers/reach.js +1 -1
  38. package/src/servers/reach.ts +1 -1
  39. package/src/servers/vps.js +1 -1
  40. package/src/servers/vps.ts +1 -1
  41. package/src/servers/wordpress.js +1 -1
  42. package/src/servers/wordpress.ts +1 -1
  43. package/types.d.ts +190 -9
package/CHANGELOG.md CHANGED
@@ -4,6 +4,31 @@ 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.39.0 — 2026-11-12
8
+
9
+ ### Operations
10
+
11
+ - Added `hosting_pocketbase_backend` — Get PocketBase backend
12
+ - Added `hosting_pocketbase_create-backend` — Create PocketBase backend
13
+ - Added `hosting_pocketbase_delete-backend` — Delete PocketBase backend
14
+ - Added `hosting_pocketbase_list-backends` — List account PocketBase backends
15
+ - Added `hosting_pocketbase_set-superuser` — Set PocketBase superuser
16
+ - Changed the description and input schema of `hosting_websites_create`
17
+ - Changed the description and input schema of `wordpress_installations_install`
18
+
19
+ ### Also in this release
20
+
21
+ - Documentation: `README.md`
22
+ - Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
23
+ - Build and packaging: `types.d.ts`
24
+
25
+ ## v3.38.4 — 2026-11-12
26
+
27
+ ### Also in this release
28
+
29
+ - Dependencies: `package-lock.json`
30
+ - Bundled agent skills: `skills/headless/VERSION`
31
+
7
32
  ## v3.38.3 — 2026-11-11
8
33
 
9
34
  ### Also in this release
package/README.md CHANGED
@@ -78,7 +78,7 @@ pnpm update -g @hostinger/mcp
78
78
 
79
79
  This package installs the following MCP server commands:
80
80
 
81
- - `hostinger-api-mcp` — unified server over every operation (409 total)
81
+ - `hostinger-api-mcp` — unified server over every operation (414 total)
82
82
  - `hostinger-agency-hosting-mcp` — 43 operations for agency-hosting
83
83
  - `hostinger-agent-readiness-mcp` — 4 operations for agent-readiness
84
84
  - `hostinger-billing-mcp` — 10 operations for billing
@@ -87,7 +87,7 @@ This package installs the following MCP server commands:
87
87
  - `hostinger-ecommerce-mcp` — 30 operations for ecommerce
88
88
  - `hostinger-gpu-mcp` — 5 operations for gpu
89
89
  - `hostinger-horizons-mcp` — 7 operations for horizons
90
- - `hostinger-hosting-mcp` — 54 operations for hosting
90
+ - `hostinger-hosting-mcp` — 59 operations for hosting
91
91
  - `hostinger-mail-mcp` — 39 operations for mail
92
92
  - `hostinger-reach-mcp` — 71 operations for reach
93
93
  - `hostinger-vps-mcp` — 68 operations for vps
@@ -2499,10 +2499,14 @@ root with the admin user, email and password from `wordpress`, the domain as the
2499
2499
  title, and `en_US` when `wordpress.language` is omitted. The headless types
2500
2500
  (`headless_empty`, `headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`)
2501
2501
  create a headless website; `headless_wordpress` additionally installs WordPress into the
2502
- `cms` directory of the website root with generated credentials. `headless_empty` installs
2503
- nothing: WordPress can be added later through
2504
- `POST /api/hosting/v1/accounts/{username}/wordpress/installations`
2505
- (`wordpress_installations_install`) with `type: headless`.
2502
+ `cms` directory of the website root with generated credentials. `headless_pocketbase`
2503
+ marks the website as a headless PocketBase website but installs nothing: create its
2504
+ PocketBase backend with `Create PocketBase backend`
2505
+ (`POST /api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase`) once the setup
2506
+ is `completed`. `headless_empty` installs nothing either: WordPress can be added later
2507
+ through `POST /api/hosting/v1/accounts/{username}/wordpress/installations`
2508
+ (`wordpress_installations_install`) with `type: headless`, or a PocketBase backend through
2509
+ the same PocketBase endpoint.
2506
2510
 
2507
2511
  Omit `domain` to set the website up on a generated temporary free subdomain; the created
2508
2512
  setup returns it as `domain`. REST clients that need to know the free subdomain before the
@@ -2555,6 +2559,117 @@ Use it to debug PHP issues or inspect the complete PHP environment of the websit
2555
2559
  - **Method**: `GET`
2556
2560
  - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/php/php-info`
2557
2561
 
2562
+ #### hosting_pocketbase_backend
2563
+
2564
+ Returns the PocketBase backend of a website: its REST API and dashboard URLs, live state
2565
+ and version. A PocketBase backend gives the website a database, authentication, file
2566
+ storage and a realtime REST API, served from the website's own domain under `/api` and
2567
+ `/_`. Returns 404 when the website has no PocketBase backend.
2568
+
2569
+ The superuser password is only shown once, when it is set, and is never returned here. If it
2570
+ is lost, set a new one with the `Set PocketBase superuser` endpoint.
2571
+
2572
+ The instance sleeps when idle and wakes on the first request, so `asleep` is a normal state
2573
+ and the first call to a sleeping instance can take a few seconds. `starting`, `running` and
2574
+ `stopping` are healthy; `failed` or `unregistered` mean the instance is broken; `missing`
2575
+ means its files are gone from the server, and creating the PocketBase backend again sets up
2576
+ a new, empty one. `state` is null when the server could not be reached; retry later.
2577
+
2578
+ PocketBase is rolling out gradually: an account without access yet gets 422.
2579
+
2580
+ - **Method**: `GET`
2581
+ - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase`
2582
+
2583
+ #### hosting_pocketbase_create-backend
2584
+
2585
+ Creates a PocketBase backend for a website: a database, authentication, file storage and a
2586
+ realtime REST API, served from the website's own domain. A website has at most one
2587
+ PocketBase backend. Creation usually takes a few seconds.
2588
+
2589
+ The backend takes over the `/api` and `/_` paths of the website: from then on requests to
2590
+ these paths and everything below them go to PocketBase, while every other path keeps
2591
+ serving the website. Do not create a backend for a website that serves its own `/api` or
2592
+ `/_` paths, because they stop working; confirm with the user before calling it. Deleting
2593
+ the backend gives both paths back to the website. Headless WordPress websites and parked
2594
+ domains are not supported; for a parked domain, use the website it is parked on. A website
2595
+ that already has a backend is rejected with 422, unless that backend is in state
2596
+ `missing`: then it is replaced with a new, empty one. A website set up with
2597
+ `type: headless_empty` becomes `headless_pocketbase`; any other website keeps its type.
2598
+
2599
+ `superuser_password` is optional: leave it out to get a strong generated password, or send
2600
+ your own (10-128 characters). The response returns it in `superuser_password` once and
2601
+ Hostinger never stores it, so save it in your app secrets right away; you need it to manage
2602
+ the backend through the PocketBase REST API. If it is lost, set a new one with the
2603
+ `Set PocketBase superuser` endpoint. `superuser_email` defaults to the email of the
2604
+ website owner.
2605
+
2606
+ The instance sleeps when idle and wakes on the first request, so the first call after a
2607
+ quiet period can take a few seconds. `next_steps` in the response lists what to do next.
2608
+
2609
+ PocketBase is rolling out gradually: an account without access yet gets 422.
2610
+
2611
+ - **Method**: `POST`
2612
+ - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase`
2613
+
2614
+ #### hosting_pocketbase_delete-backend
2615
+
2616
+ Permanently deletes the PocketBase backend of a website with all its data (collections,
2617
+ records, users and uploaded files) and gives the `/api` and `/_` paths back to the website;
2618
+ a `headless_pocketbase` website becomes `headless_empty`. This cannot be undone and every
2619
+ app using this backend stops working, so confirm with the user before calling it and
2620
+ export the data you need from the dashboard (`admin_url`) first.
2621
+
2622
+ Returns success also when the website has no PocketBase backend; then it only clears a
2623
+ `headless_pocketbase` mark. To regain access after losing the superuser password, use the
2624
+ `Set PocketBase superuser` endpoint instead of deleting the backend.
2625
+
2626
+ PocketBase is rolling out gradually: an account without access yet gets 422; an unknown
2627
+ website gets 404.
2628
+
2629
+ - **Method**: `DELETE`
2630
+ - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase`
2631
+
2632
+ #### hosting_pocketbase_list-backends
2633
+
2634
+ Lists the PocketBase backends of all websites of a hosting account with their URLs, live
2635
+ state, version and disk usage. A PocketBase backend gives a website a database,
2636
+ authentication, file storage and a realtime REST API, served from the website's own
2637
+ domain. An empty list means no website of the account has a PocketBase backend.
2638
+
2639
+ States: `asleep` is normal (the instance sleeps when idle and wakes on the first request);
2640
+ `starting`, `running` and `stopping` are healthy; `failed` or `unregistered` mean the
2641
+ instance is broken; `missing` means its files are gone from the server, and creating the
2642
+ PocketBase backend again sets up a new, empty one. `state` is null when the server could
2643
+ not be reached; retry later.
2644
+
2645
+ PocketBase is rolling out gradually: an account without access yet gets 422.
2646
+
2647
+ - **Method**: `GET`
2648
+ - **Path**: `/api/hosting/v1/accounts/{username}/pocketbase`
2649
+
2650
+ #### hosting_pocketbase_set-superuser
2651
+
2652
+ Sets the password of a superuser of the website's PocketBase backend, and creates that
2653
+ superuser when there is none with the given email. The old password of that superuser stops
2654
+ working at once, so apps and scripts still using it lose superuser access; confirm with the
2655
+ user before calling it.
2656
+
2657
+ Use it when the superuser password is lost (Hostinger never stores it), when it leaked and
2658
+ must be rotated, or to add another superuser with a different email. Returns 404 when the
2659
+ website has no PocketBase backend; create one first. App user accounts are managed through
2660
+ the PocketBase REST API, not here.
2661
+
2662
+ `superuser_password` is optional: leave it out to get a strong generated password, or send
2663
+ your own (10-128 characters). The response returns it in `superuser_password` once and
2664
+ Hostinger never stores it, so save it in your app secrets right away, then authenticate
2665
+ again with `pb.collection('_superusers').authWithPassword`. `superuser_email` defaults to
2666
+ the email of the website owner.
2667
+
2668
+ PocketBase is rolling out gradually: an account without access yet gets 422.
2669
+
2670
+ - **Method**: `PUT`
2671
+ - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase/superuser`
2672
+
2558
2673
  #### hosting_redirects_list-website
2559
2674
 
2560
2675
  Returns a paginated list of redirects configured for the selected website.
@@ -4779,9 +4894,11 @@ Send `type: headless` to turn a headless website (for example one created by
4779
4894
  `hosting_websites_create` with `type: headless_empty`) into a headless WordPress
4780
4895
  website: WordPress is installed into the `cms` directory with the Hostinger headless
4781
4896
  MU plugin and the website is marked as a headless WordPress website. `directory` is
4782
- not allowed with it. The target website must already be headless: the headless
4783
- install rewrites the root `.htaccess`, so on any other website the request is
4784
- rejected with 422.
4897
+ not allowed with it. The target website must be an empty headless website
4898
+ (`headless_empty`): the headless install rewrites the root `.htaccess`, so any other
4899
+ website, including a headless website that already has WordPress or a PocketBase
4900
+ backend, is rejected with 422. To replace a PocketBase backend with WordPress, delete
4901
+ it first with `Delete PocketBase backend`.
4785
4902
 
4786
4903
  Call GET /api/hosting/v1/wordpress/installations (`wordpress_installations_list`)
4787
4904
  filtered by username and domain before proceeding to check whether WordPress is
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hostinger-api-mcp",
3
- "version": "3.38.3",
3
+ "version": "3.39.0",
4
4
  "description": "Hostinger API — manage domains, DNS, hosting, VPS, billing and more from Gemini CLI.",
5
5
  "mcpServers": {
6
6
  "hostinger": {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hostinger/mcp",
3
- "version": "3.38.3",
3
+ "version": "3.39.0",
4
4
  "mcpName": "io.github.hostinger/hostinger-api-mcp",
5
5
  "description": "MCP server for Hostinger API",
6
6
  "repository": {
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.38.3",
20
+ "version": "3.39.0",
21
21
  "packages": [
22
22
  {
23
23
  "registryType": "npm",
24
24
  "identifier": "@hostinger/mcp",
25
- "version": "3.38.3",
25
+ "version": "3.39.0",
26
26
  "transport": {
27
27
  "type": "stdio"
28
28
  },
@@ -1,3 +1,3 @@
1
- version=3.38.3
2
- commit=9b497d4052aa
3
- built=2026-11-11
1
+ version=3.39.0
2
+ commit=49930122d23b
3
+ built=2026-11-12
@@ -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.13.1
65
+ * Generated from OpenAPI spec version 2.14.0
66
66
  */
67
67
  class MCPServer {
68
68
  constructor({ name, version, tools, instructions, skills = [] }) {
@@ -96,7 +96,7 @@ interface Skill { uri: string; frontmatter: Record<string, unknown>; resources:
96
96
 
97
97
  /**
98
98
  * MCP Server for Hostinger API
99
- * Generated from OpenAPI spec version 2.13.1
99
+ * Generated from OpenAPI spec version 2.14.0
100
100
  */
101
101
  class MCPServer {
102
102
  private readonly name: string;
@@ -9386,7 +9386,7 @@ export default [
9386
9386
  "readOnlyHint": false,
9387
9387
  "destructiveHint": false
9388
9388
  },
9389
- "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint (`hosting_websites_list-setups`) with the `domain` filter every 10 to 15\nseconds and wait for `status: completed` before uploading files, deploying or creating\ndatabases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_empty`, `headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`)\ncreate a headless website; `headless_wordpress` additionally installs WordPress into the\n`cms` directory of the website root with generated credentials. `headless_empty` installs\nnothing: WordPress can be added later through\n`POST /api/hosting/v1/accounts/{username}/wordpress/installations`\n(`wordpress_installations_install`) with `type: headless`.\n\nOmit `domain` to set the website up on a generated temporary free subdomain; the created\nsetup returns it as `domain`. REST clients that need to know the free subdomain before the\ncall, so a timed-out call can be looked up and retried on the same domain, can generate\none through `POST /api/hosting/v1/domains/free-subdomains` and send it as `domain`. It is\naccepted for 24 hours, only from the client that generated it.\n\nWhen the order has no hosting account yet, the setup creates one first, in the datacenter\ngiven by `datacenter_code` or the order's default datacenter when it is omitted.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
9389
+ "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint (`hosting_websites_list-setups`) with the `domain` filter every 10 to 15\nseconds and wait for `status: completed` before uploading files, deploying or creating\ndatabases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_empty`, `headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`)\ncreate a headless website; `headless_wordpress` additionally installs WordPress into the\n`cms` directory of the website root with generated credentials. `headless_pocketbase`\nmarks the website as a headless PocketBase website but installs nothing: create its\nPocketBase backend with `Create PocketBase backend`\n(`POST /api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase`) once the setup\nis `completed`. `headless_empty` installs nothing either: WordPress can be added later\nthrough `POST /api/hosting/v1/accounts/{username}/wordpress/installations`\n(`wordpress_installations_install`) with `type: headless`, or a PocketBase backend through\nthe same PocketBase endpoint.\n\nOmit `domain` to set the website up on a generated temporary free subdomain; the created\nsetup returns it as `domain`. REST clients that need to know the free subdomain before the\ncall, so a timed-out call can be looked up and retried on the same domain, can generate\none through `POST /api/hosting/v1/domains/free-subdomains` and send it as `domain`. It is\naccepted for 24 hours, only from the client that generated it.\n\nWhen the order has no hosting account yet, the setup creates one first, in the datacenter\ngiven by `datacenter_code` or the order's default datacenter when it is omitted.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
9390
9390
  "method": "POST",
9391
9391
  "path": "/api/hosting/v1/orders/{order_id}/onboardings",
9392
9392
  "inputSchema": {
@@ -9398,7 +9398,7 @@ export default [
9398
9398
  },
9399
9399
  "type": {
9400
9400
  "type": "string",
9401
- "description": "Website type. Omit or `null` for an empty website. `wordpress` installs WordPress in the website root and requires `wordpress`. The headless types (`headless_empty`, `headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless website; `headless_wordpress` additionally installs WordPress into the `cms` directory with generated credentials. `headless_empty` installs nothing, so WordPress can be added later through `POST /api/hosting/v1/accounts/{username}/wordpress/installations` (`wordpress_installations_install`) with `type: headless`.",
9401
+ "description": "Website type. Omit or `null` for an empty website. `wordpress` installs WordPress in the website root and requires `wordpress`. The headless types (`headless_empty`, `headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless website; `headless_wordpress` additionally installs WordPress into the `cms` directory with generated credentials. `headless_pocketbase` only marks the website as a headless PocketBase website: create the backend afterwards with `Create PocketBase backend` (`POST /api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase`). `headless_empty` installs nothing, so WordPress can be added later through `POST /api/hosting/v1/accounts/{username}/wordpress/installations` (`wordpress_installations_install`) with `type: headless`, or a PocketBase backend through the PocketBase endpoint.",
9402
9402
  "enum": [
9403
9403
  "wordpress",
9404
9404
  "headless_empty",
@@ -9766,6 +9766,194 @@ export default [
9766
9766
  "group": "hosting",
9767
9767
  "hidden": true
9768
9768
  },
9769
+ {
9770
+ "name": "hosting_pocketbase_backend",
9771
+ "title": "Get PocketBase backend",
9772
+ "annotations": {
9773
+ "title": "Get PocketBase backend",
9774
+ "readOnlyHint": true,
9775
+ "destructiveHint": false
9776
+ },
9777
+ "description": "Returns the PocketBase backend of a website: its REST API and dashboard URLs, live state\nand version. A PocketBase backend gives the website a database, authentication, file\nstorage and a realtime REST API, served from the website's own domain under `/api` and\n`/_`. Returns 404 when the website has no PocketBase backend.\n\nThe superuser password is only shown once, when it is set, and is never returned here. If it\nis lost, set a new one with the `Set PocketBase superuser` endpoint.\n\nThe instance sleeps when idle and wakes on the first request, so `asleep` is a normal state\nand the first call to a sleeping instance can take a few seconds. `starting`, `running` and\n`stopping` are healthy; `failed` or `unregistered` mean the instance is broken; `missing`\nmeans its files are gone from the server, and creating the PocketBase backend again sets up\na new, empty one. `state` is null when the server could not be reached; retry later.\n\nPocketBase is rolling out gradually: an account without access yet gets 422.",
9778
+ "method": "GET",
9779
+ "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase",
9780
+ "inputSchema": {
9781
+ "type": "object",
9782
+ "properties": {
9783
+ "username": {
9784
+ "type": "string",
9785
+ "description": "username parameter"
9786
+ },
9787
+ "domain": {
9788
+ "type": "string",
9789
+ "description": "Domain name"
9790
+ }
9791
+ },
9792
+ "required": [
9793
+ "username",
9794
+ "domain"
9795
+ ]
9796
+ },
9797
+ "security": [
9798
+ {
9799
+ "apiToken": []
9800
+ }
9801
+ ],
9802
+ "group": "hosting"
9803
+ },
9804
+ {
9805
+ "name": "hosting_pocketbase_create-backend",
9806
+ "title": "Create PocketBase backend",
9807
+ "annotations": {
9808
+ "title": "Create PocketBase backend",
9809
+ "readOnlyHint": false,
9810
+ "destructiveHint": false
9811
+ },
9812
+ "description": "Creates a PocketBase backend for a website: a database, authentication, file storage and a\nrealtime REST API, served from the website's own domain. A website has at most one\nPocketBase backend. Creation usually takes a few seconds.\n\nThe backend takes over the `/api` and `/_` paths of the website: from then on requests to\nthese paths and everything below them go to PocketBase, while every other path keeps\nserving the website. Do not create a backend for a website that serves its own `/api` or\n`/_` paths, because they stop working; confirm with the user before calling it. Deleting\nthe backend gives both paths back to the website. Headless WordPress websites and parked\ndomains are not supported; for a parked domain, use the website it is parked on. A website\nthat already has a backend is rejected with 422, unless that backend is in state\n`missing`: then it is replaced with a new, empty one. A website set up with\n`type: headless_empty` becomes `headless_pocketbase`; any other website keeps its type.\n\n`superuser_password` is optional: leave it out to get a strong generated password, or send\nyour own (10-128 characters). The response returns it in `superuser_password` once and\nHostinger never stores it, so save it in your app secrets right away; you need it to manage\nthe backend through the PocketBase REST API. If it is lost, set a new one with the\n`Set PocketBase superuser` endpoint. `superuser_email` defaults to the email of the\nwebsite owner.\n\nThe instance sleeps when idle and wakes on the first request, so the first call after a\nquiet period can take a few seconds. `next_steps` in the response lists what to do next.\n\nPocketBase is rolling out gradually: an account without access yet gets 422.",
9813
+ "method": "POST",
9814
+ "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase",
9815
+ "inputSchema": {
9816
+ "type": "object",
9817
+ "properties": {
9818
+ "username": {
9819
+ "type": "string",
9820
+ "description": "username parameter"
9821
+ },
9822
+ "domain": {
9823
+ "type": "string",
9824
+ "description": "Domain name"
9825
+ },
9826
+ "superuser_email": {
9827
+ "type": "string",
9828
+ "description": "Email of the PocketBase superuser. Defaults to the email of the website owner."
9829
+ },
9830
+ "superuser_password": {
9831
+ "type": "string",
9832
+ "description": "Password for the PocketBase superuser, 10-128 characters. Leave it out to have a strong one\ngenerated. Either way it is returned once in the response and never stored."
9833
+ }
9834
+ },
9835
+ "required": [
9836
+ "username",
9837
+ "domain"
9838
+ ]
9839
+ },
9840
+ "security": [
9841
+ {
9842
+ "apiToken": []
9843
+ }
9844
+ ],
9845
+ "group": "hosting"
9846
+ },
9847
+ {
9848
+ "name": "hosting_pocketbase_delete-backend",
9849
+ "title": "Delete PocketBase backend",
9850
+ "annotations": {
9851
+ "title": "Delete PocketBase backend",
9852
+ "readOnlyHint": false,
9853
+ "destructiveHint": true,
9854
+ "idempotentHint": true
9855
+ },
9856
+ "description": "Permanently deletes the PocketBase backend of a website with all its data (collections,\nrecords, users and uploaded files) and gives the `/api` and `/_` paths back to the website;\na `headless_pocketbase` website becomes `headless_empty`. This cannot be undone and every\napp using this backend stops working, so confirm with the user before calling it and\nexport the data you need from the dashboard (`admin_url`) first.\n\nReturns success also when the website has no PocketBase backend; then it only clears a\n`headless_pocketbase` mark. To regain access after losing the superuser password, use the\n`Set PocketBase superuser` endpoint instead of deleting the backend.\n\nPocketBase is rolling out gradually: an account without access yet gets 422; an unknown\nwebsite gets 404.",
9857
+ "method": "DELETE",
9858
+ "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase",
9859
+ "inputSchema": {
9860
+ "type": "object",
9861
+ "properties": {
9862
+ "username": {
9863
+ "type": "string",
9864
+ "description": "username parameter"
9865
+ },
9866
+ "domain": {
9867
+ "type": "string",
9868
+ "description": "Domain name"
9869
+ }
9870
+ },
9871
+ "required": [
9872
+ "username",
9873
+ "domain"
9874
+ ]
9875
+ },
9876
+ "security": [
9877
+ {
9878
+ "apiToken": []
9879
+ }
9880
+ ],
9881
+ "group": "hosting"
9882
+ },
9883
+ {
9884
+ "name": "hosting_pocketbase_list-backends",
9885
+ "title": "List account PocketBase backends",
9886
+ "annotations": {
9887
+ "title": "List account PocketBase backends",
9888
+ "readOnlyHint": true,
9889
+ "destructiveHint": false
9890
+ },
9891
+ "description": "Lists the PocketBase backends of all websites of a hosting account with their URLs, live\nstate, version and disk usage. A PocketBase backend gives a website a database,\nauthentication, file storage and a realtime REST API, served from the website's own\ndomain. An empty list means no website of the account has a PocketBase backend.\n\nStates: `asleep` is normal (the instance sleeps when idle and wakes on the first request);\n`starting`, `running` and `stopping` are healthy; `failed` or `unregistered` mean the\ninstance is broken; `missing` means its files are gone from the server, and creating the\nPocketBase backend again sets up a new, empty one. `state` is null when the server could\nnot be reached; retry later.\n\nPocketBase is rolling out gradually: an account without access yet gets 422.",
9892
+ "method": "GET",
9893
+ "path": "/api/hosting/v1/accounts/{username}/pocketbase",
9894
+ "inputSchema": {
9895
+ "type": "object",
9896
+ "properties": {
9897
+ "username": {
9898
+ "type": "string",
9899
+ "description": "username parameter"
9900
+ }
9901
+ },
9902
+ "required": [
9903
+ "username"
9904
+ ]
9905
+ },
9906
+ "security": [
9907
+ {
9908
+ "apiToken": []
9909
+ }
9910
+ ],
9911
+ "group": "hosting"
9912
+ },
9913
+ {
9914
+ "name": "hosting_pocketbase_set-superuser",
9915
+ "title": "Set PocketBase superuser",
9916
+ "annotations": {
9917
+ "title": "Set PocketBase superuser",
9918
+ "readOnlyHint": false,
9919
+ "destructiveHint": true,
9920
+ "idempotentHint": true
9921
+ },
9922
+ "description": "Sets the password of a superuser of the website's PocketBase backend, and creates that\nsuperuser when there is none with the given email. The old password of that superuser stops\nworking at once, so apps and scripts still using it lose superuser access; confirm with the\nuser before calling it.\n\nUse it when the superuser password is lost (Hostinger never stores it), when it leaked and\nmust be rotated, or to add another superuser with a different email. Returns 404 when the\nwebsite has no PocketBase backend; create one first. App user accounts are managed through\nthe PocketBase REST API, not here.\n\n`superuser_password` is optional: leave it out to get a strong generated password, or send\nyour own (10-128 characters). The response returns it in `superuser_password` once and\nHostinger never stores it, so save it in your app secrets right away, then authenticate\nagain with `pb.collection('_superusers').authWithPassword`. `superuser_email` defaults to\nthe email of the website owner.\n\nPocketBase is rolling out gradually: an account without access yet gets 422.",
9923
+ "method": "PUT",
9924
+ "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase/superuser",
9925
+ "inputSchema": {
9926
+ "type": "object",
9927
+ "properties": {
9928
+ "username": {
9929
+ "type": "string",
9930
+ "description": "username parameter"
9931
+ },
9932
+ "domain": {
9933
+ "type": "string",
9934
+ "description": "Domain name"
9935
+ },
9936
+ "superuser_email": {
9937
+ "type": "string",
9938
+ "description": "Email of the superuser to create or update. Defaults to the email of the website owner."
9939
+ },
9940
+ "superuser_password": {
9941
+ "type": "string",
9942
+ "description": "New password of the PocketBase superuser, 10-128 characters. Leave it out to have a strong\none generated. Either way it is returned once in the response and never stored."
9943
+ }
9944
+ },
9945
+ "required": [
9946
+ "username",
9947
+ "domain"
9948
+ ]
9949
+ },
9950
+ "security": [
9951
+ {
9952
+ "apiToken": []
9953
+ }
9954
+ ],
9955
+ "group": "hosting"
9956
+ },
9769
9957
  {
9770
9958
  "name": "hosting_redirects_list-website",
9771
9959
  "title": "List website redirects",
@@ -17850,7 +18038,7 @@ export default [
17850
18038
  "readOnlyHint": false,
17851
18039
  "destructiveHint": false
17852
18040
  },
17853
- "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/orders/{order_id}/onboardings\n(`hosting_websites_create`) and poll GET /api/hosting/v1/onboardings\n(`hosting_websites_list-setups`) with the `domain` filter until its `status` is\n`completed`.\n\nSend `type: headless` to turn a headless website (for example one created by\n`hosting_websites_create` with `type: headless_empty`) into a headless WordPress\nwebsite: WordPress is installed into the `cms` directory with the Hostinger headless\nMU plugin and the website is marked as a headless WordPress website. `directory` is\nnot allowed with it. The target website must already be headless: the headless\ninstall rewrites the root `.htaccess`, so on any other website the request is\nrejected with 422.\n\nCall GET /api/hosting/v1/wordpress/installations (`wordpress_installations_list`)\nfiltered by username and domain before proceeding to check whether WordPress is\nalready installed on the target domain/path. If WordPress already exists and\n`overwrite` is false (the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations\n(`wordpress_installations_list`) filtered by username and domain to track\nprogress. When the installation appears in that list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
18041
+ "description": "Install WordPress on an existing website.\n\nThe website must already exist before calling this endpoint. To create a new\nwebsite first, use POST /api/hosting/v1/orders/{order_id}/onboardings\n(`hosting_websites_create`) and poll GET /api/hosting/v1/onboardings\n(`hosting_websites_list-setups`) with the `domain` filter until its `status` is\n`completed`.\n\nSend `type: headless` to turn a headless website (for example one created by\n`hosting_websites_create` with `type: headless_empty`) into a headless WordPress\nwebsite: WordPress is installed into the `cms` directory with the Hostinger headless\nMU plugin and the website is marked as a headless WordPress website. `directory` is\nnot allowed with it. The target website must be an empty headless website\n(`headless_empty`): the headless install rewrites the root `.htaccess`, so any other\nwebsite, including a headless website that already has WordPress or a PocketBase\nbackend, is rejected with 422. To replace a PocketBase backend with WordPress, delete\nit first with `Delete PocketBase backend`.\n\nCall GET /api/hosting/v1/wordpress/installations (`wordpress_installations_list`)\nfiltered by username and domain before proceeding to check whether WordPress is\nalready installed on the target domain/path. If WordPress already exists and\n`overwrite` is false (the default), the async job will fail.\n\nThis operation is asynchronous: a successful response only means the install\njob has been queued, not that WordPress is ready. Installation typically\ntakes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations\n(`wordpress_installations_list`) filtered by username and domain to track\nprogress. When the installation appears in that list, WordPress is ready.\n\nReturns 422 when the account already uses all the databases its plan allows,\nunless `database.name` is an existing database on the account.",
17854
18042
  "method": "POST",
17855
18043
  "path": "/api/hosting/v1/accounts/{username}/wordpress/installations",
17856
18044
  "inputSchema": {
@@ -17874,7 +18062,7 @@ export default [
17874
18062
  },
17875
18063
  "type": {
17876
18064
  "type": "string",
17877
- "description": "Installation kind; `default` when omitted. `headless` installs WordPress into the `cms` directory with the Hostinger headless MU plugin and marks the website as a headless WordPress website. Accepted only for a website that is already headless, e.g. one created by `POST /api/hosting/v1/orders/{order_id}/onboardings` (`hosting_websites_create`) with `type: headless_empty`; any other website is rejected with 422.",
18065
+ "description": "Installation kind; `default` when omitted. `headless` installs WordPress into the `cms` directory with the Hostinger headless MU plugin and marks the website as a headless WordPress website. Accepted only for an empty headless website, e.g. one created by `POST /api/hosting/v1/orders/{order_id}/onboardings` (`hosting_websites_create`) with `type: headless_empty`; any other website, including a headless website that already has WordPress or a PocketBase backend, is rejected with 422.",
17878
18066
  "enum": [
17879
18067
  "default",
17880
18068
  "headless"