DealCloud APIConnect DealCloud without building on its API
DealCloud has a REST API. Customers only: a user in a group with the 'API' site-area capability (enabled by a DealCloud admin or CSM) turns on an API key in their profile. If you're reading the docs because you need DealCloud 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 DealCloud and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0 client credentials
- AccessSelf-serve for customers
What the DealCloud API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 client credentials (client ID + user API key exchanged for a 15-minute bearer token)
- Who can get access
- Customers only: a user in a group with the 'API' site-area capability (enabled by a DealCloud admin or CSM) turns on an API key in their profile.
- What it covers
- Schema (entry types, fields), data (rows/cells, history, files, merge, template reports), user management, publications (event streams), backups, and relationship-intelligence import.
- Limits
- 5 requests/second for Data, Schema, User Management and RelIntel endpoints, 300/minute for the token endpoint, and 1,000/second for Publications and eMarketing.
Official docs: api.docs.dealcloud.com. Checked September 2026. Vendors change access terms, so confirm with DealCloud before you build.
Building on the DealCloud API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get DealCloud credentials, and manage tokens and refreshes. | Connect your DealCloud 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 DealCloud 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 DealCloud work off someone's desk, the build is the slow part.
What teams usually want the DealCloud API for
Activity capture
Caddi logs emails and meetings to the right DealCloud company and deal record, with the participants and next steps attached.
Dedupe and source attribution
Caddi merges duplicate records and attributes deal source consistently so origination reporting holds up.
Pipeline reporting pack
Caddi assembles the weekly pipeline pack from DealCloud and distributes it to the investment committee.
DealCloud API questions
Does DealCloud have an API?
Yes. DealCloud has a REST API, authenticated with OAuth 2.0 client credentials (client ID + user API key exchanged for a 15-minute bearer token). The official documentation is at https://api.docs.dealcloud.com/.
How do I get access to the DealCloud API?
Customers only: a user in a group with the 'API' site-area capability (enabled by a DealCloud admin or CSM) turns on an API key in their profile.
Does the DealCloud API have rate limits?
5 requests/second for Data, Schema, User Management and RelIntel endpoints, 300/minute for the token endpoint, and 1,000/second for Publications and eMarketing.
Can I connect DealCloud to my other tools without writing code against its API?
Yes. With Caddi you show the DealCloud task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across DealCloud 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 DealCloud with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for DealCloud is reviewed before it runs in production, and every run is logged.
Connect DealCloud without the build.
Drop your work email and pick a time. We'll show you Caddi running your DealCloud workflow end to end.