Datto Autotask PSA: What URL do I use to connect to the Autotask API?



What URL do I use to connect to the Autotask API?


  • Datto Autotask PSA


Autotask has multiple zones. The zones are generally, allocated geographically, but exceptions are possible. The zone number appears in the customer's Autotask URL.

Autotask product releases do not go out to all zones at the same time. Some zones will have a newer version of the application and the API since the API is always current for the Autotask version in that zone. As a result, there will be some unavoidable differences between versions of the WSDL. This difference is most noticeable between the localized and English versions.

  • Currently, you can anticipate a time lag of 4 – 8 weeks after a significant English release is completed. The release would be before new features and other changes are delivered in the German and Spanish language zones.
  • For maintenance releases, anticipate a time lag of 1 -2 weeks. If you bind your code to the Pre-Release WSDL for development and testing, anticipate the time lag before you make the updated code available to users residing in different zones. An alternative would be to bind your code to the WSDL for that zone. You can then detect and correct for any differences.
  • You can determine the WSDL version using the getWsdlVersion() call. 
  • You can no longer generate the "auto-generated" WSDL file from the URL: https://webservices[n].autotask.net/atservices/1.5/atws.asmx?wsdl
    • [n] is your Autotask zone.

To avoid problems when you make your code available to customers in multiple zones, do the following:

In your development environment, create a proxy class (Web Reference) for the Autotask Web Services API by referencing the WSDL file. The appropriate URL is determined by your Autotask zone.

Note: You can not connect to the URLs below using a browser window. Only via programmatic authentication from an application or integration.

Zone Variations for the URL Of The WSDL File For Version 1.6

Zone URL of the WSDL file
Pre-release https://webservices2.autotask.net/atservices/1.6/atws.wsdl
Pre-release (UK) https://webservices11.autotask.net/atservices/1.6/atws.wsdl
Limited Release https://webservices1.autotask.net/atservices/1.6/atws.wsdl
Limited Release (UK) https://webservices17.autotask.net/atservices/1.6/atws.wsdl
America East
America East 2
America West https://webservices5.autotask.net/atservices/1.6/atws.wsdl
America West 2 https://webservices15.autotask.net/atservices/1.6/atws.wsdl
UK https://webservices4.autotask.net/atservices/1.6/atws.wsdl
UK2 https://webservices16.autotask.net/atservices/1.6/atws.wsdl
Australia / New Zealand https://webservices6.autotask.net/atservices/1.6/atws.wsdl
PRDE https://prde.autotask.net/ATServices/1.6/atws.wsdl
PRES https://pres.autotask.net/ATServices/1.6/atws.wsdl
German (Deutsch) https://webservices18.autotask.net/atservices/1.6/atws.wsdl
EU1 (English Europe and Asia) https://webservices19.autotask.net/atservices/1.6/atws.wsdl
Spanish (Español)

To determine the proper zone (and accompanying URL) to use for all API interactions

  1. Set up your application so that getZoneInfo() is the first call made.
  2. Direct the getZoneInfo call to:

If you bound your code to an English language WSDL for development and testing

  1. Before you make your code available to users in any localized zone, bind your code to the WSDL for that particular zone. You can detect and correct for any differences.
    • We recommend that, when writing your applications, you store the URL information in an initialization or configuration file.
      • For example, .NET developers can store the information in the Web.config file. This allows for easy updating if the URL information changes.

Anticipate regular updates and the release of new versions of the Web Service API

New versions will, for the most part, support backward compatibility through multiple releases, but there may be changes to functionality that have an impact on your application. Please check Autotask release notes and any additional notifications that provide information on Web Services changes and updates.

  • We strongly suggest that you update your application with each Web Service API release, or monitor the impact that changes might have on your application and plan accordingly, especially if Autotask plans to remove support for the API version that you are using.

Additional Resources

Was this article helpful?

0 out of 0 found this helpful

You must sign in before voting on this article.

Want to talk about it? Have a feature request?

Head on over to our Community Forum or get live help.

Datto Homepage