hostinger-api-mcp 1.28.0 → 1.30.0

package/types.d.ts

@@ -1232,6 +1232,167 @@ for example when the confirmation email cannot be received, without waiting out
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Retrieve the incoming move for a specified domain.
+
+Returns 404 when no account is moving this domain to you.
+
+Use this endpoint to check whether a domain addressed to you is still waiting to be accepted.
+   */
+  "domains_getIncomingDomainMoveV1": {
+    params: {
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Re-check the move against the registry before responding. Only has an effect while the move is in the `activating` status.
+       */
+      force_sync?: boolean;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Accept an incoming move for a specified domain.
+
+The provided WHOIS profiles become the contacts of the domain, so they must belong
+to your account and satisfy the requirements of the TLD. Only the contact types the
+domain actually uses are applied, but all four profile IDs have to be provided.
+
+The move has to still be waiting for your decision, already accepted moves
+cannot be accepted again.
+
+Accepting does not complete the move. A confirmation email is sent to the email address of
+the new owner contact, and the domain changes hands only after the change is confirmed from it.
+Until then the move stays in the `activating` status, which can be followed with the
+[incoming move endpoint](#tag/domains-move).
+
+Use this endpoint to take ownership of a domain offered to you.
+   */
+  "domains_acceptIncomingDomainMoveV1": {
+    params: {
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * WHOIS profiles of the accepting account. Only the contact types required by the TLD are applied, but all four IDs must be provided.
+       */
+      domain_contacts: object;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Reject an incoming move for a specified domain.
+
+The domain stays in the account which initiated the move.
+Moves you have already accepted cannot be rejected anymore.
+
+Use this endpoint to decline a domain you do not want to take over.
+   */
+  "domains_rejectIncomingDomainMoveV1": {
+    params: {
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Retrieve all domains other Hostinger accounts are moving to your account.
+
+Moves of every status are returned, including the ones which already completed.
+
+Use this endpoint to find domains waiting for you to accept them.
+   */
+  "domains_getIncomingDomainMoveListV1": {
+    params: {
+
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Retrieve the outgoing move for a specified domain.
+
+Returns 404 when the domain has no move in progress.
+
+Use this endpoint to track the status of a move you have initiated for a single domain.
+   */
+  "domains_getOutgoingDomainMoveV1": {
+    params: {
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Initiate a move of a specified domain to another Hostinger account.
+
+The receiving account has to already exist and accept the move before the domain changes hands.
+
+The domain must be active. The subscription it belongs to is resolved automatically,
+and the request is rejected with a 404 status code when the domain has no domain
+subscription of its own.
+
+Domains protected by premium protection require an additional verification step,
+such requests are rejected with a 428 status code.
+
+Use this endpoint to hand a domain over to another Hostinger user.
+   */
+  "domains_startOutgoingDomainMoveV1": {
+    params: {
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Email address of the Hostinger account receiving the domain
+       */
+      new_customer_email: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Cancel an outgoing move for a specified domain.
+
+The move can only be cancelled while the receiving account has not accepted it yet.
+The domain stays in your account.
+
+Use this endpoint to withdraw a move you no longer want to complete.
+   */
+  "domains_cancelOutgoingDomainMoveV1": {
+    params: {
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Retrieve all domains you are moving to other Hostinger accounts.
+
+Only moves which have not completed yet are returned.
+
+Use this endpoint to track moves you have initiated and the accounts they are addressed to.
+   */
+  "domains_getOutgoingDomainMoveListV1": {
+    params: {
+
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve the authorization (EPP) code for a specified domain so it can be transferred
 away from Hostinger to another registrar.
@@ -1250,6 +1411,43 @@ Use this endpoint to obtain the code required to transfer a domain to another re
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Claim a free domain available on your account and register it.
+
+Unlike purchasing a domain, this consumes a free domain you already have,
+so no payment method is required.
+
+A successful response means the domain is registered. If registration fails, login to
+[hPanel](https://hpanel.hostinger.com/) and check domain registration status.
+
+If no WHOIS information is provided, default contact information for that TLD will be used.
+Before making request, ensure WHOIS information for desired TLD exists in your account.
+
+Some TLDs require `additional_details` to be provided and these will be validated before claiming.
+
+Requests which cannot be fulfilled are rejected with an error code in the response body,
+for example `2037` when no free domain is available.
+
+Use this endpoint to register a domain using a free domain from your account.
+   */
+  "domains_claimFreeDomainV1": {
+    params: {
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Domain contact information
+       */
+      domain_contacts?: object;
+      /**
+       * Additional registration data, possible values depends on TLD
+       */
+      additional_details?: object;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Enable domain lock for the domain.
 
@@ -1439,6 +1637,48 @@ Use this endpoint to configure custom DNS hosting for domains.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Claim a free domain transfer available on your account and start the transfer.
+
+Unlike purchasing a transfer, this consumes a free domain transfer you already have,
+so no payment method is required.
+
+Before making request, unlock the domain at the current registrar and get its authorization
+code. The transfer is validated first, so domains which cannot be transferred are rejected
+before the free domain transfer is consumed.
+
+A successful response means the transfer has been started. Completion depends on the current
+registrar and can be followed with the [transfer list endpoint](#tag/domains-transfer).
+
+If no WHOIS information is provided, default contact information for that TLD will be used.
+Before making request, ensure WHOIS information for desired TLD exists in your account.
+
+Requests which cannot be fulfilled are rejected with an error code in the response body.
+
+Use this endpoint to transfer a domain using a free domain transfer from your account.
+   */
+  "domains_claimFreeDomainTransferV1": {
+    params: {
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Authorization code from the current registrar
+       */
+      auth_code: string;
+      /**
+       * Domain contact information
+       */
+      domain_contacts?: object;
+      /**
+       * Keep the existing nameservers of the domain
+       */
+      should_keep_ns?: boolean;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve the transfer for a specified domain.