Action is required for customers doing custom integrations that are not managed by Innotas. This applies to WSAPI integrations only, not Single-Sign On/SAML. No change required if your integration was custom-built by Innotas, and Innotas is managing the integration.
api.innotas.com will no longer respond to requests after March 16, 2018 10pm PT.
Innotas is making some changes to handling of API traffic that will result in lower latency connections and eliminate single points of failure. As a result, you need to change the endpoints of your integrations that currently use api.innotas.com to use your DNS subdomain (myCompany.innotas.com). You can verify your subdomain by logging in and checking the URL; note that sandboxes and production environments will have different subdomains (for example, myCompany.innotas.com and myCompany-sb.innotas.com).
You can view the Innotas WSDL at: https://<yourcompanysubdomain>.innotas.com/services/MainService?wsdl>
Please use either one of these endpoints (be sure to replace "myCompany" with your DNS subdomain name):
<wsdl:port name="MainServiceHttpsSoap11Endpoint" binding="ns:MainServiceSoap11Binding">
<wsdl:port name="MainServiceHttpsSoap12Endpoint" binding="ns:MainServiceSoap12Binding">
Note: As you're updating your endpoint, please remember that we are retiring support for TLS 1.0. As discussed in the article TLS 1.0 End of Life, you will need to update your development platform to TLS 1.1 or 1.2 by June 15 - you might want to take care of it all at once.