For your initial setup, follow on with our Getting Started Guide
Step 1: Creating an API User
- Follow the Autotask instructions for – Adding or editing an API user (autotask.net)
- Navigation: Autotask menu > Admin > Account Settings & Users > Resources/Users (HR) > Resources/Users > New > New API User.
- Navigation: Autotask menu > Admin > Account Settings & Users > Resources/Users (HR) > Resources/Users > New > New API User.
- Ensure you select Sync 365 License from the Integration Vendor dropdown
- Assign a default system API levelto the API user.
- If you need additional security, ensure the user has the following permissions:
- Navigation: Autotask menu > Admin > Account Settings & Users > Resources/Users (HR) > Security > Security Levels
Header Item Permissions Contracts Contracts View - All, Add - Yes Contracts Can modify Service/Bundle on contract charges Selected Contracts Contract Visibility Full CRM Customer & Cancellations All CRM Accounts Add - Yes, Edit - Yes CRM Contacts Add - Yes Inventory Items View - All Inventory Products View - All Inventory Product notes edit Add - Yes, Edit - All Admin Accounts & Contacts Selected Admin Products, Services & Inventory Selected Admin Contracts & Un-Posting Selected Service Desk Tickets View - All, Add/edit - Yes Web Services API Can login to Web Services API Selected
- Generate a Key and Secret
- Record these details to enter later
Step 2: Adding Autotask to Sync 365 License
- Log in to the Sync 365 portal at sync.s365l.com
- Click on Tools > Integration Settings
- Click the + next to PSA Tools
- Select Autotask as the PSA Type
Enter the Webservices Zone:
Check your Autotask URL (e.g.,
ww2.autotask.net
). Enter "webservices2" in the Zone field if your URL starts withww2
.
- Enter the Username and Secret for the API user.
- Click Test and Save Credentials
- The platform will verify the connection and then retrieve the latest data from Autotask.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article