IT Glue APIConnect IT Glue without building on its API
IT Glue has a REST API. Customers on the Enterprise plan only, with keys generated by users with the Administrator role. If you're reading the docs because you need IT Glue 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 IT Glue and your other tools.
- APIREST (JSON)
- AuthAPI key
- AccessPlan-dependent
What the IT Glue API gives you
- Type
- REST (JSON)
- Authentication
- API key (x-api-key header)
- Who can get access
- Customers on the Enterprise plan only, with keys generated by users with the Administrator role.
- What it covers
- Organizations, configurations, passwords, documents, flexible assets, contacts, locations, checklists, and users.
- Limits
- 3,000 requests per 5-minute window, with 429 on excess.
- Worth knowing
- Some objects cannot be updated via the API when they are synced from a PSA.
Official docs: api.itglue.com. Checked September 2026. Vendors change access terms, so confirm with IT Glue before you build.
Building on the IT Glue API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get IT Glue credentials, and manage tokens and refreshes. | Connect your IT Glue 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 IT Glue 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 IT Glue work off someone's desk, the build is the slow part.
What teams usually want the IT Glue API for
Onboarding documentation
Caddi assembles client and configuration records and writes the matching IT Glue documentation during onboarding.
Documentation sync
Caddi keeps IT Glue in sync with your PSA and RMM so records reflect the current state.
IT Glue API questions
Does IT Glue have an API?
Yes. IT Glue has a REST API, authenticated with API key (x-api-key header). The official documentation is at https://api.itglue.com/developer/.
How do I get access to the IT Glue API?
Customers on the Enterprise plan only, with keys generated by users with the Administrator role.
Does the IT Glue API have rate limits?
3,000 requests per 5-minute window, with 429 on excess.
Can I connect IT Glue to my other tools without writing code against its API?
Yes. With Caddi you show the IT Glue task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across IT Glue 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 IT Glue with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for IT Glue is reviewed before it runs in production, and every run is logged.
Connect IT Glue without the build.
Drop your work email and pick a time. We'll show you Caddi running your IT Glue workflow end to end.