hostinger-api-mcp 1.27.1 → 1.29.0

package/types.d.ts

@@ -1199,6 +1199,200 @@ Use this endpoint to set up domain redirects to other URLs.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Retrieve a pending IRTP verification for a domain.
+
+Both the old and new registrant must confirm it before the WHOIS change takes effect.
+
+Use this endpoint to check the status of a WHOIS change awaiting registrant confirmation.
+   */
+  "domains_getPendingIRTPVerificationV1": {
+    params: {
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Cancel a pending IRTP verification.
+
+Use this endpoint to back out of a WHOIS change that is stuck waiting on registrant confirmation,
+for example when the confirmation email cannot be received, without waiting out the 5-day expiry.
+   */
+  "domains_cancelPendingIRTPVerificationV1": {
+    params: {
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    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.
@@ -1434,18 +1628,32 @@ Use this endpoint to monitor incoming and outgoing registrar transfers across yo
   };
 
   /**
-   * Unset WHOIS contact profile as default.
+   * Change WHOIS contact profile for a domain.
 
-The profile itself is kept, it is only no longer pre-selected for its TLD.
+Repoints the given contact roles to a new WHOIS profile and submits the change to the registry.
+The profile currently assigned to those roles is resolved automatically;
+the request fails if the given roles are not all on the same profile today.
 
-Use this endpoint to stop reusing contact information for new registrations.
+Changing transfer sensitive fields on the owner contact starts an IRTP verification.
+
+The change is processed asynchronously.
+
+Use this endpoint to move a registered domain onto different contact information.
    */
-  "domains_unsetDefaultWHOISProfileV1": {
+  "domains_changeWHOISProfileForDomainV1": {
     params: {
       /**
-       * WHOIS ID
+       * WHOIS profile ID to assign to the domain
        */
-      whoisId: number;
+      new_whois_id: number;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Contact roles to repoint to the new WHOIS profile
+       */
+      change_for: array;
     };
     response: any; // Response structure will depend on the API
   };
@@ -1467,6 +1675,23 @@ Use this endpoint to avoid picking contact information for every registration.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Unset WHOIS contact profile as default.
+
+The profile itself is kept, it is only no longer pre-selected for its TLD.
+
+Use this endpoint to stop reusing contact information for new registrations.
+   */
+  "domains_unsetDefaultWHOISProfileV1": {
+    params: {
+      /**
+       * WHOIS ID
+       */
+      whoisId: number;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve a WHOIS contact profile.