reselling enom service nightmare

[d3m0n]

introduction

We have been happily using and reselling enom domains for almost 25 years now and never had to contact support . And for over a year we have been reselling g suite . So we decided to give it a shot and add enoms email service to a package and integrate their business email service and offer it to our customers. We have developed a microservice a simple solution that creates service and adds mailboxes using their official API As a dealer and client of Enom with over 25 year , we recently decided to actively engage in the distribution of Enom services, particularly the resale of email services. However, as we gradually began to sell these services, we encountered significant difficulties.

After one month we have experienced a complete deletion of all mailboxes for all  domains , they just expired despite our renewal attempts  being set to auto-renew and credits being deducted from the account according to the official manual. While we are in the beta mode and we have created only 30 mailboxes  and is not financially significant, we lost all his data and correspondence,

What concerns me most is the response from tech support in resolving this issue. Over two weeks, various specialists assured us that someone would contact us or provide an answer and we should wait until the issue is being resolved by the devs, yet the problem remains unresolved. Not only have we been unable to restore the data, but we also cannot recreate all these accounts again.

How can we confidently invest in promoting this service if such a fundamental task takes weeks to resolve? What will happen if we encounter similar issues with hundreds or thousands of clients?

 

 

Here are few simples API requests that we are using:

Here is a request example:

1) PurchaseServices - https://reseller.enom.com/interface.asp?command=PurchaseServices&Service=pop3&QuantityUnit=boxes&BillingPeriod=month&TimeQuantity=1&uid=ourid&pw=OurPassword&sld=domain&tld=com&responsetype=xml

 

2) SetupPop3user - https://reseller.enom.com/interface.asp?command=SetupPop3user&uid=ourid&pw=OurPassword&sld=domain&tld=com&BundleID=1838223&UserName1=oksana.savielieva&Password1=NFTE$ix20240626!&DisplayName1=oksana+savielieva&responsetype=xml

 

After a month just a few days before the we send a request to a customer and if they agree to renew we send a request to eNom

2) For renewing we are using the "SETPAKRENEW" for 1 month ( with API )

Here is a an example: https://reseller.enom.com/interface.asp?command=SETPAKRENEW&uid=ourid&pw=OurPassword&sld=domain&tld=com&bundleid=1838223&AutoPakRenew=1&responsetype=xml

 

The outcome:

On  7/23/2024 we have sent renew request (SETPAKRENEW) for add expiration also 1 month (8/26/2024), but it's added expiration to wrong bundleId's. Instead of the ones were trying to renew 

 Our 30 mailboxes have expired with client data lost

We are not able to renew them , we can't add expiration (1 month with API),

We can't remove them because there is no API to remove mailboxes

We can’t create new mailboxes with same name to override 

Looks like Enom support doesn’t really know how their product API works , they give us false hints that don’t work at the end of the day , they promise  us to wait and that the devs will contact us soon

There is no resolution for more than two weeks

If there is anybody that has experience with enom api , we would highly appreciate any help because we are lost , stuck and frustrated