Autotask APIConnect Autotask without building on its API
Autotask has a REST API. Self-serve for customers only, using an 'API User (API-only)' security-level resource, which has no per-seat charge. If you're reading the docs because you need Autotask to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Autotask and your other tools.
- APIREST (JSON)
- AuthAPI user credentials in headers
- AccessSelf-serve for customers
What the Autotask API gives you
- Type
- REST (JSON)
- Authentication
- API user credentials in headers (username, secret and API integration code)
- Who can get access
- Self-serve for customers only, using an 'API User (API-only)' security-level resource, which has no per-seat charge.
- What it covers
- PSA entities such as companies, contacts, tickets, projects, time entries, contracts and billing.
- Limits
- 10,000 requests per hour per database, with added latency above 50% of that threshold and at most 500 records returned per query.
Official docs: autotask.net. Checked September 2026. Vendors change access terms, so confirm with Autotask before you build.
Building on the Autotask API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Autotask credentials, and manage tokens and refreshes. | Connect your Autotask account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Autotask task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Autotask work off someone's desk, the build is the slow part.
What teams usually want the Autotask API for
Request to ticket
Caddi turns inbound email and alerts into correctly-routed Autotask tickets with the right queue, priority, and contract.
Time & billing sync
Caddi reconciles time entries and contracts against Autotask and posts invoice-ready records to accounting.
Autotask API questions
Does Autotask have an API?
Yes. Autotask has a REST API, authenticated with API user credentials in headers (username, secret and API integration code). The official documentation is at https://www.autotask.net/help/developerhelp/Content/APIs/REST/General_Topics/REST_Security_Auth.htm.
How do I get access to the Autotask API?
Self-serve for customers only, using an 'API User (API-only)' security-level resource, which has no per-seat charge.
Does the Autotask API have rate limits?
10,000 requests per hour per database, with added latency above 50% of that threshold and at most 500 records returned per query.
Can I connect Autotask to my other tools without writing code against its API?
Yes. With Caddi you show the Autotask task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Autotask and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Autotask with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Autotask is reviewed before it runs in production, and every run is logged.
Connect Autotask without the build.
Drop your work email and pick a time. We'll show you Caddi running your Autotask workflow end to end.