hey try removng the smtptoken key if not needed, it might be conflicting with newer validtion rules; check the latest api dox for proper parameter usage. hope that hlps
In my experience, the error regarding invalid parameters when registering a domain is often due to subtle changes in the API’s expected input format. I encountered a similar situation where an extra field not recognized by the latest API version caused the issue. It is advisable to consult the most recent API documentation to confirm which parameters are necessary. Even if a field was required previously, updates might have deprecated or altered its expected usage, leading to conflicts during registration. Ensuring consistency with the current parameter schema proved to be the solution in my case.
hey, try droppin the smtp token. i had a similar issue and removin it fixed my problem. make sure your domain & api token are up to spec with the new docs. hope it helps!
The issue might be related to changes in parameter naming conventions or required values between different versions of the API. In my experience, making sure that only the expected parameters are used based on the most current API documentation is crucial. I encountered a similar problem when integrating a similar service and found that removing or renaming the smtpToken field resolved the issue. It could also be that additional server-side checks are being performed, so reviewing the schema defined in the latest docs might be the best approach.