hostinger-api-mcp 1.32.0 → 1.33.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/types.d.ts CHANGED
@@ -664,9 +664,9 @@ status, metadata, hosting plan details, and resource quotas.
664
664
  };
665
665
 
666
666
  /**
667
- * Deletes an Agency Plan website and schedules cleanup of its resources.
668
-
669
- This action is irreversible. Website files, databases, and linked domains are removed.
667
+ * Permanently deletes an Agency Plan website. Deletion is processed asynchronously: the
668
+ website is immediately transitioned to a deleting state and the underlying server
669
+ resources are removed in the background.
670
670
  */
671
671
  "agency-hosting_deleteAgencyPlanWebsiteV1": {
672
672
  params: {
@@ -4565,6 +4565,10 @@ and a confirmation email will be sent.
4565
4565
  * Get a list of all contact segments.
4566
4566
 
4567
4567
  This endpoint returns a list of contact segments that can be used to organize contacts.
4568
+
4569
+ **Deprecated.** This endpoint cannot target a profile, so it always falls back to
4570
+ the client's default profile and cannot list the segments of any other profile. Use
4571
+ `GET /api/reach/v1/profiles/{profileUuid}/segmentation/segments` instead.
4568
4572
  */
4569
4573
  "reach_listSegmentsV1": {
4570
4574
  params: {
@@ -4578,6 +4582,10 @@ This endpoint returns a list of contact segments that can be used to organize co
4578
4582
 
4579
4583
  This endpoint allows creating a new contact segment that can be used to organize contacts.
4580
4584
  The segment can be configured with specific criteria like email, name, subscription status, etc.
4585
+
4586
+ **Deprecated.** This endpoint cannot target a profile, so it always falls back to
4587
+ the client's default profile and cannot create segments in any other profile. Use
4588
+ `POST /api/reach/v1/profiles/{profileUuid}/segmentation/segments` instead.
4581
4589
  */
4582
4590
  "reach_createANewContactSegmentV1": {
4583
4591
  params: {
@@ -4597,6 +4605,25 @@ The segment can be configured with specific criteria like email, name, subscript
4597
4605
  response: any; // Response structure will depend on the API
4598
4606
  };
4599
4607
 
4608
+ /**
4609
+ * Count the contacts currently matching a segment without listing them.
4610
+
4611
+ Cheaper than paging through the segment contacts endpoint when only the size is needed.
4612
+ */
4613
+ "reach_countProfileSegmentContactsV1": {
4614
+ params: {
4615
+ /**
4616
+ * Profile uuid parameter
4617
+ */
4618
+ profileUuid: string;
4619
+ /**
4620
+ * Segment uuid parameter
4621
+ */
4622
+ segmentUuid: string;
4623
+ };
4624
+ response: any; // Response structure will depend on the API
4625
+ };
4626
+
4600
4627
  /**
4601
4628
  * Retrieve contacts associated with a specific segment for a given profile.
4602
4629
 
@@ -4625,11 +4652,144 @@ identified by its UUID, scoped to a specific profile.
4625
4652
  response: any; // Response structure will depend on the API
4626
4653
  };
4627
4654
 
4655
+ /**
4656
+ * Get a single segment of a profile, including the conditions that define it.
4657
+
4658
+ To retrieve the contacts currently matching those conditions, use the segment contacts
4659
+ endpoint instead.
4660
+ */
4661
+ "reach_getProfileSegmentDetailsV1": {
4662
+ params: {
4663
+ /**
4664
+ * Profile uuid parameter
4665
+ */
4666
+ profileUuid: string;
4667
+ /**
4668
+ * Segment uuid parameter
4669
+ */
4670
+ segmentUuid: string;
4671
+ };
4672
+ response: any; // Response structure will depend on the API
4673
+ };
4674
+
4675
+ /**
4676
+ * Rename a segment and/or replace the conditions that define it.
4677
+
4678
+ `name` is always required. Omit `conditions` to rename without touching the conditions;
4679
+ supply them and they replace the existing set entirely rather than being merged into it.
4680
+ Contacts are never modified, but which of them match the segment can change immediately.
4681
+ */
4682
+ "reach_updateAProfileSegmentV1": {
4683
+ params: {
4684
+ /**
4685
+ * Profile uuid parameter
4686
+ */
4687
+ profileUuid: string;
4688
+ /**
4689
+ * Segment uuid parameter
4690
+ */
4691
+ segmentUuid: string;
4692
+ /**
4693
+ * name parameter
4694
+ */
4695
+ name: string;
4696
+ /**
4697
+ * Replaces the existing conditions entirely. Omit to keep the current ones.
4698
+ */
4699
+ conditions?: array;
4700
+ /**
4701
+ * How to combine multiple conditions. Required when conditions are given.
4702
+ */
4703
+ logic?: string;
4704
+ };
4705
+ response: any; // Response structure will depend on the API
4706
+ };
4707
+
4708
+ /**
4709
+ * Delete a segment.
4710
+
4711
+ Only the segment definition is removed. The contacts that matched it are left untouched.
4712
+ */
4713
+ "reach_deleteAProfileSegmentV1": {
4714
+ params: {
4715
+ /**
4716
+ * Profile uuid parameter
4717
+ */
4718
+ profileUuid: string;
4719
+ /**
4720
+ * Segment uuid parameter
4721
+ */
4722
+ segmentUuid: string;
4723
+ };
4724
+ response: any; // Response structure will depend on the API
4725
+ };
4726
+
4727
+ /**
4728
+ * Get a paginated list of the segments defined in a profile.
4729
+
4730
+ Each entry carries the number of contacts currently matching it, which is recalculated on
4731
+ read rather than stored. Use `count_type` to count either every matching contact or only
4732
+ the subscribed ones.
4733
+ */
4734
+ "reach_listProfileSegmentsV1": {
4735
+ params: {
4736
+ /**
4737
+ * Profile uuid parameter
4738
+ */
4739
+ profileUuid: string;
4740
+ /**
4741
+ * Which matching contacts to count for each segment
4742
+ */
4743
+ count_type?: string;
4744
+ /**
4745
+ * Page number
4746
+ */
4747
+ page?: number;
4748
+ /**
4749
+ * Number of items per page
4750
+ */
4751
+ per_page?: number;
4752
+ };
4753
+ response: any; // Response structure will depend on the API
4754
+ };
4755
+
4756
+ /**
4757
+ * Create a segment in a profile.
4758
+
4759
+ A segment is a saved set of conditions rather than a fixed list, so its membership changes
4760
+ as contacts change. Creating one does not modify any contact.
4761
+ */
4762
+ "reach_createAProfileSegmentV1": {
4763
+ params: {
4764
+ /**
4765
+ * Profile uuid parameter
4766
+ */
4767
+ profileUuid: string;
4768
+ /**
4769
+ * name parameter
4770
+ */
4771
+ name: string;
4772
+ /**
4773
+ * Conditions a contact must satisfy to fall into the segment
4774
+ */
4775
+ conditions: array;
4776
+ /**
4777
+ * How to combine multiple conditions
4778
+ */
4779
+ logic: string;
4780
+ };
4781
+ response: any; // Response structure will depend on the API
4782
+ };
4783
+
4628
4784
  /**
4629
4785
  * Retrieve contacts associated with a specific segment.
4630
4786
 
4631
4787
  This endpoint allows you to fetch and filter contacts that belong to a particular segment,
4632
4788
  identified by its UUID.
4789
+
4790
+ **Deprecated.** This endpoint cannot target a profile, so it always falls back to
4791
+ the client's default profile and cannot read segments of any other profile. Use
4792
+ `GET /api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}/contacts` instead.
4633
4793
  */
4634
4794
  "reach_listSegmentContactsV1": {
4635
4795
  params: {
@@ -4654,6 +4814,10 @@ identified by its UUID.
4654
4814
 
4655
4815
  This endpoint retrieves information about a single segment identified by UUID.
4656
4816
  Segments are used to organize and group contacts based on specific criteria.
4817
+
4818
+ **Deprecated.** This endpoint cannot target a profile, so it always falls back to
4819
+ the client's default profile and cannot read segments of any other profile. Use
4820
+ `GET /api/reach/v1/profiles/{profileUuid}/segmentation/segments/{segmentUuid}` instead.
4657
4821
  */
4658
4822
  "reach_getSegmentDetailsV1": {
4659
4823
  params: {