ServiceNow APIConnect ServiceNow without building on its API
ServiceNow has REST and SOAP APIs. Customers use the APIs on their own instance, and any developer can sign up for the free Developer Program and get a Personal Developer Instance. If you're reading the docs because you need ServiceNow 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 ServiceNow and your other tools.
- APIREST + SOAP
- AuthBasic authentication or OAuth 2.0
- AccessSelf-serve for customers
What the ServiceNow API gives you
- Type
- REST + SOAP
- Authentication
- Basic authentication or OAuth 2.0
- Who can get access
- Customers use the APIs on their own instance, and any developer can sign up for the free Developer Program and get a Personal Developer Instance.
- What it covers
- Any platform table through the Table API (incidents, changes, CMDB CIs, users and so on), plus attachments, import sets, aggregates and custom Scripted REST APIs.
- Limits
- No fixed global limit is documented; instance admins set per-hour inbound REST limits in the Rate Limit Rules table (sys_rate_limit_rules), and requests over the limit get HTTP 429 with Retry-After.
Official docs: developer.servicenow.com. Checked September 2026. Vendors change access terms, so confirm with ServiceNow before you build.
Building on the ServiceNow API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get ServiceNow credentials, and manage tokens and refreshes. | Connect your ServiceNow 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 ServiceNow 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 ServiceNow work off someone's desk, the build is the slow part.
What teams usually want the ServiceNow API for
Intake to incident
Caddi reads inbound email and forms, classifies them, and creates the matching ServiceNow incident or request with the right assignment group.
Cross-system sync
Caddi keeps ServiceNow records in lockstep with your CRM and other systems so the same update never has to be entered twice.
ServiceNow API questions
Does ServiceNow have an API?
Yes. ServiceNow has REST and SOAP APIs, authenticated with Basic authentication or OAuth 2.0. The official documentation is at https://developer.servicenow.com/dev.do#!/reference/api/latest/rest/.
How do I get access to the ServiceNow API?
Customers use the APIs on their own instance, and any developer can sign up for the free Developer Program and get a Personal Developer Instance.
Does the ServiceNow API have rate limits?
No fixed global limit is documented; instance admins set per-hour inbound REST limits in the Rate Limit Rules table (sys_rate_limit_rules), and requests over the limit get HTTP 429 with Retry-After.
Can I connect ServiceNow to my other tools without writing code against its API?
Yes. With Caddi you show the ServiceNow task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across ServiceNow 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 ServiceNow with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for ServiceNow is reviewed before it runs in production, and every run is logged.
Connect ServiceNow without the build.
Drop your work email and pick a time. We'll show you Caddi running your ServiceNow workflow end to end.