Freshservice APIConnect Freshservice without building on its API
Freshservice has a REST API. Self-serve for customers only (each agent's personal API key); rate limits are documented for all plans from Starter to Enterprise. If you're reading the docs because you need Freshservice 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 Freshservice and your other tools.
- APIREST (JSON)
- AuthAPI key
- AccessSelf-serve for customers
What the Freshservice API gives you
- Type
- REST (JSON)
- Authentication
- API key (sent via HTTP basic auth)
- Who can get access
- Self-serve for customers only (each agent's personal API key); rate limits are documented for all plans from Starter to Enterprise.
- What it covers
- ITSM objects such as tickets, problems, changes, releases, assets, requesters, agents and the service catalog.
- Limits
- Account-wide limits of 100/200/400/500 requests per minute on Starter/Growth/Pro/Enterprise, with sub-limits on some endpoints.
Official docs: api.freshservice.com. Checked September 2026. Vendors change access terms, so confirm with Freshservice before you build.
Building on the Freshservice API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Freshservice credentials, and manage tokens and refreshes. | Connect your Freshservice 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 Freshservice 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 Freshservice work off someone's desk, the build is the slow part.
What teams usually want the Freshservice API for
Email to ticket
Caddi turns inbound email into correctly-categorized Freshservice tickets, routed to the right group with the right priority.
Asset & approval workflows
Caddi runs asset updates and approval chains from Freshservice data and routes the output to the right owner.
Freshservice API questions
Does Freshservice have an API?
Yes. Freshservice has a REST API, authenticated with API key (sent via HTTP basic auth). The official documentation is at https://api.freshservice.com/.
How do I get access to the Freshservice API?
Self-serve for customers only (each agent's personal API key); rate limits are documented for all plans from Starter to Enterprise.
Does the Freshservice API have rate limits?
Account-wide limits of 100/200/400/500 requests per minute on Starter/Growth/Pro/Enterprise, with sub-limits on some endpoints.
Can I connect Freshservice to my other tools without writing code against its API?
Yes. With Caddi you show the Freshservice task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Freshservice 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 Freshservice with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Freshservice is reviewed before it runs in production, and every run is logged.
Connect Freshservice without the build.
Drop your work email and pick a time. We'll show you Caddi running your Freshservice workflow end to end.