@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
@@ -9405,7 +9405,7 @@ const tools: OpenApiTool[] = [
9405
9405
  "readOnlyHint": false,
9406
9406
  "destructiveHint": false
9407
9407
  },
9408
- "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.",
9408
+ "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.",
9409
9409
  "method": "POST",
9410
9410
  "path": "/api/hosting/v1/orders/{order_id}/onboardings",
9411
9411
  "inputSchema": {
@@ -9417,7 +9417,7 @@ const tools: OpenApiTool[] = [
9417
9417
  },
9418
9418
  "type": {
9419
9419
  "type": "string",
9420
- "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`.",
9420
+ "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.",
9421
9421
  "enum": [
9422
9422
  "wordpress",
9423
9423
  "headless_empty",
@@ -9785,6 +9785,194 @@ const tools: OpenApiTool[] = [
9785
9785
  "group": "hosting",
9786
9786
  "hidden": true
9787
9787
  },
9788
+ {
9789
+ "name": "hosting_pocketbase_backend",
9790
+ "title": "Get PocketBase backend",
9791
+ "annotations": {
9792
+ "title": "Get PocketBase backend",
9793
+ "readOnlyHint": true,
9794
+ "destructiveHint": false
9795
+ },
9796
+ "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.",
9797
+ "method": "GET",
9798
+ "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase",
9799
+ "inputSchema": {
9800
+ "type": "object",
9801
+ "properties": {
9802
+ "username": {
9803
+ "type": "string",
9804
+ "description": "username parameter"
9805
+ },
9806
+ "domain": {
9807
+ "type": "string",
9808
+ "description": "Domain name"
9809
+ }
9810
+ },
9811
+ "required": [
9812
+ "username",
9813
+ "domain"
9814
+ ]
9815
+ },
9816
+ "security": [
9817
+ {
9818
+ "apiToken": []
9819
+ }
9820
+ ],
9821
+ "group": "hosting"
9822
+ },
9823
+ {
9824
+ "name": "hosting_pocketbase_create-backend",
9825
+ "title": "Create PocketBase backend",
9826
+ "annotations": {
9827
+ "title": "Create PocketBase backend",
9828
+ "readOnlyHint": false,
9829
+ "destructiveHint": false
9830
+ },
9831
+ "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.",
9832
+ "method": "POST",
9833
+ "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase",
9834
+ "inputSchema": {
9835
+ "type": "object",
9836
+ "properties": {
9837
+ "username": {
9838
+ "type": "string",
9839
+ "description": "username parameter"
9840
+ },
9841
+ "domain": {
9842
+ "type": "string",
9843
+ "description": "Domain name"
9844
+ },
9845
+ "superuser_email": {
9846
+ "type": "string",
9847
+ "description": "Email of the PocketBase superuser. Defaults to the email of the website owner."
9848
+ },
9849
+ "superuser_password": {
9850
+ "type": "string",
9851
+ "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."
9852
+ }
9853
+ },
9854
+ "required": [
9855
+ "username",
9856
+ "domain"
9857
+ ]
9858
+ },
9859
+ "security": [
9860
+ {
9861
+ "apiToken": []
9862
+ }
9863
+ ],
9864
+ "group": "hosting"
9865
+ },
9866
+ {
9867
+ "name": "hosting_pocketbase_delete-backend",
9868
+ "title": "Delete PocketBase backend",
9869
+ "annotations": {
9870
+ "title": "Delete PocketBase backend",
9871
+ "readOnlyHint": false,
9872
+ "destructiveHint": true,
9873
+ "idempotentHint": true
9874
+ },
9875
+ "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.",
9876
+ "method": "DELETE",
9877
+ "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase",
9878
+ "inputSchema": {
9879
+ "type": "object",
9880
+ "properties": {
9881
+ "username": {
9882
+ "type": "string",
9883
+ "description": "username parameter"
9884
+ },
9885
+ "domain": {
9886
+ "type": "string",
9887
+ "description": "Domain name"
9888
+ }
9889
+ },
9890
+ "required": [
9891
+ "username",
9892
+ "domain"
9893
+ ]
9894
+ },
9895
+ "security": [
9896
+ {
9897
+ "apiToken": []
9898
+ }
9899
+ ],
9900
+ "group": "hosting"
9901
+ },
9902
+ {
9903
+ "name": "hosting_pocketbase_list-backends",
9904
+ "title": "List account PocketBase backends",
9905
+ "annotations": {
9906
+ "title": "List account PocketBase backends",
9907
+ "readOnlyHint": true,
9908
+ "destructiveHint": false
9909
+ },
9910
+ "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.",
9911
+ "method": "GET",
9912
+ "path": "/api/hosting/v1/accounts/{username}/pocketbase",
9913
+ "inputSchema": {
9914
+ "type": "object",
9915
+ "properties": {
9916
+ "username": {
9917
+ "type": "string",
9918
+ "description": "username parameter"
9919
+ }
9920
+ },
9921
+ "required": [
9922
+ "username"
9923
+ ]
9924
+ },
9925
+ "security": [
9926
+ {
9927
+ "apiToken": []
9928
+ }
9929
+ ],
9930
+ "group": "hosting"
9931
+ },
9932
+ {
9933
+ "name": "hosting_pocketbase_set-superuser",
9934
+ "title": "Set PocketBase superuser",
9935
+ "annotations": {
9936
+ "title": "Set PocketBase superuser",
9937
+ "readOnlyHint": false,
9938
+ "destructiveHint": true,
9939
+ "idempotentHint": true
9940
+ },
9941
+ "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.",
9942
+ "method": "PUT",
9943
+ "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase/superuser",
9944
+ "inputSchema": {
9945
+ "type": "object",
9946
+ "properties": {
9947
+ "username": {
9948
+ "type": "string",
9949
+ "description": "username parameter"
9950
+ },
9951
+ "domain": {
9952
+ "type": "string",
9953
+ "description": "Domain name"
9954
+ },
9955
+ "superuser_email": {
9956
+ "type": "string",
9957
+ "description": "Email of the superuser to create or update. Defaults to the email of the website owner."
9958
+ },
9959
+ "superuser_password": {
9960
+ "type": "string",
9961
+ "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."
9962
+ }
9963
+ },
9964
+ "required": [
9965
+ "username",
9966
+ "domain"
9967
+ ]
9968
+ },
9969
+ "security": [
9970
+ {
9971
+ "apiToken": []
9972
+ }
9973
+ ],
9974
+ "group": "hosting"
9975
+ },
9788
9976
  {
9789
9977
  "name": "hosting_redirects_list-website",
9790
9978
  "title": "List website redirects",
@@ -17869,7 +18057,7 @@ const tools: OpenApiTool[] = [
17869
18057
  "readOnlyHint": false,
17870
18058
  "destructiveHint": false
17871
18059
  },
17872
- "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.",
18060
+ "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.",
17873
18061
  "method": "POST",
17874
18062
  "path": "/api/hosting/v1/accounts/{username}/wordpress/installations",
17875
18063
  "inputSchema": {
@@ -17893,7 +18081,7 @@ const tools: OpenApiTool[] = [
17893
18081
  },
17894
18082
  "type": {
17895
18083
  "type": "string",
17896
- "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.",
18084
+ "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.",
17897
18085
  "enum": [
17898
18086
  "default",
17899
18087
  "headless"
@@ -3531,7 +3531,7 @@ export default [
3531
3531
  "readOnlyHint": false,
3532
3532
  "destructiveHint": false
3533
3533
  },
3534
- "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.",
3534
+ "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.",
3535
3535
  "method": "POST",
3536
3536
  "path": "/api/hosting/v1/orders/{order_id}/onboardings",
3537
3537
  "inputSchema": {
@@ -3543,7 +3543,7 @@ export default [
3543
3543
  },
3544
3544
  "type": {
3545
3545
  "type": "string",
3546
- "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`.",
3546
+ "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.",
3547
3547
  "enum": [
3548
3548
  "wordpress",
3549
3549
  "headless_empty",
@@ -3911,6 +3911,194 @@ export default [
3911
3911
  "group": "hosting",
3912
3912
  "hidden": true
3913
3913
  },
3914
+ {
3915
+ "name": "hosting_pocketbase_backend",
3916
+ "title": "Get PocketBase backend",
3917
+ "annotations": {
3918
+ "title": "Get PocketBase backend",
3919
+ "readOnlyHint": true,
3920
+ "destructiveHint": false
3921
+ },
3922
+ "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.",
3923
+ "method": "GET",
3924
+ "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase",
3925
+ "inputSchema": {
3926
+ "type": "object",
3927
+ "properties": {
3928
+ "username": {
3929
+ "type": "string",
3930
+ "description": "username parameter"
3931
+ },
3932
+ "domain": {
3933
+ "type": "string",
3934
+ "description": "Domain name"
3935
+ }
3936
+ },
3937
+ "required": [
3938
+ "username",
3939
+ "domain"
3940
+ ]
3941
+ },
3942
+ "security": [
3943
+ {
3944
+ "apiToken": []
3945
+ }
3946
+ ],
3947
+ "group": "hosting"
3948
+ },
3949
+ {
3950
+ "name": "hosting_pocketbase_create-backend",
3951
+ "title": "Create PocketBase backend",
3952
+ "annotations": {
3953
+ "title": "Create PocketBase backend",
3954
+ "readOnlyHint": false,
3955
+ "destructiveHint": false
3956
+ },
3957
+ "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.",
3958
+ "method": "POST",
3959
+ "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase",
3960
+ "inputSchema": {
3961
+ "type": "object",
3962
+ "properties": {
3963
+ "username": {
3964
+ "type": "string",
3965
+ "description": "username parameter"
3966
+ },
3967
+ "domain": {
3968
+ "type": "string",
3969
+ "description": "Domain name"
3970
+ },
3971
+ "superuser_email": {
3972
+ "type": "string",
3973
+ "description": "Email of the PocketBase superuser. Defaults to the email of the website owner."
3974
+ },
3975
+ "superuser_password": {
3976
+ "type": "string",
3977
+ "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."
3978
+ }
3979
+ },
3980
+ "required": [
3981
+ "username",
3982
+ "domain"
3983
+ ]
3984
+ },
3985
+ "security": [
3986
+ {
3987
+ "apiToken": []
3988
+ }
3989
+ ],
3990
+ "group": "hosting"
3991
+ },
3992
+ {
3993
+ "name": "hosting_pocketbase_delete-backend",
3994
+ "title": "Delete PocketBase backend",
3995
+ "annotations": {
3996
+ "title": "Delete PocketBase backend",
3997
+ "readOnlyHint": false,
3998
+ "destructiveHint": true,
3999
+ "idempotentHint": true
4000
+ },
4001
+ "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.",
4002
+ "method": "DELETE",
4003
+ "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase",
4004
+ "inputSchema": {
4005
+ "type": "object",
4006
+ "properties": {
4007
+ "username": {
4008
+ "type": "string",
4009
+ "description": "username parameter"
4010
+ },
4011
+ "domain": {
4012
+ "type": "string",
4013
+ "description": "Domain name"
4014
+ }
4015
+ },
4016
+ "required": [
4017
+ "username",
4018
+ "domain"
4019
+ ]
4020
+ },
4021
+ "security": [
4022
+ {
4023
+ "apiToken": []
4024
+ }
4025
+ ],
4026
+ "group": "hosting"
4027
+ },
4028
+ {
4029
+ "name": "hosting_pocketbase_list-backends",
4030
+ "title": "List account PocketBase backends",
4031
+ "annotations": {
4032
+ "title": "List account PocketBase backends",
4033
+ "readOnlyHint": true,
4034
+ "destructiveHint": false
4035
+ },
4036
+ "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.",
4037
+ "method": "GET",
4038
+ "path": "/api/hosting/v1/accounts/{username}/pocketbase",
4039
+ "inputSchema": {
4040
+ "type": "object",
4041
+ "properties": {
4042
+ "username": {
4043
+ "type": "string",
4044
+ "description": "username parameter"
4045
+ }
4046
+ },
4047
+ "required": [
4048
+ "username"
4049
+ ]
4050
+ },
4051
+ "security": [
4052
+ {
4053
+ "apiToken": []
4054
+ }
4055
+ ],
4056
+ "group": "hosting"
4057
+ },
4058
+ {
4059
+ "name": "hosting_pocketbase_set-superuser",
4060
+ "title": "Set PocketBase superuser",
4061
+ "annotations": {
4062
+ "title": "Set PocketBase superuser",
4063
+ "readOnlyHint": false,
4064
+ "destructiveHint": true,
4065
+ "idempotentHint": true
4066
+ },
4067
+ "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.",
4068
+ "method": "PUT",
4069
+ "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/pocketbase/superuser",
4070
+ "inputSchema": {
4071
+ "type": "object",
4072
+ "properties": {
4073
+ "username": {
4074
+ "type": "string",
4075
+ "description": "username parameter"
4076
+ },
4077
+ "domain": {
4078
+ "type": "string",
4079
+ "description": "Domain name"
4080
+ },
4081
+ "superuser_email": {
4082
+ "type": "string",
4083
+ "description": "Email of the superuser to create or update. Defaults to the email of the website owner."
4084
+ },
4085
+ "superuser_password": {
4086
+ "type": "string",
4087
+ "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."
4088
+ }
4089
+ },
4090
+ "required": [
4091
+ "username",
4092
+ "domain"
4093
+ ]
4094
+ },
4095
+ "security": [
4096
+ {
4097
+ "apiToken": []
4098
+ }
4099
+ ],
4100
+ "group": "hosting"
4101
+ },
3914
4102
  {
3915
4103
  "name": "hosting_redirects_list-website",
3916
4104
  "title": "List website redirects",