Carta APIConnect Carta without building on its API
Carta has a REST API. Self-serve developer portal and playground, but production keys come only after Carta reviews a production access request (typically 1-2 weeks). If you're reading the docs because you need Carta 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 Carta and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessApproval required
What the Carta API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 (authorization code and client credentials)
- Who can get access
- Self-serve developer portal and playground, but production keys come only after Carta reviews a production access request (typically 1-2 weeks).
- What it covers
- Equity data through the Launch, Investor, Issuer, Portfolio, and CRM API suites (cap tables, stakeholders, securities, funds, investments).
- Limits
- Up to 10 requests/second and 300 requests/minute.
Official docs: docs.carta.com. Checked September 2026. Vendors change access terms, so confirm with Carta before you build.
Building on the Carta API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Carta credentials, and manage tokens and refreshes. | Connect your Carta 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 Carta 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 Carta work off someone's desk, the build is the slow part.
What teams usually want the Carta API for
Transaction to cap table
Caddi reads the executed document and updates the matching Carta records, routing anything ambiguous to a human.
Equity events to payroll and books
Caddi syncs exercises, vesting, and grants to payroll and the general ledger with the right coding.
Investor and valuation reporting
Caddi assembles the reporting pack from Carta on schedule and distributes it to the right recipients.
Carta API questions
Does Carta have an API?
Yes. Carta has a REST API, authenticated with OAuth 2.0 (authorization code and client credentials). The official documentation is at https://docs.carta.com/api-platform/guides/getting-started/introduction/.
How do I get access to the Carta API?
Self-serve developer portal and playground, but production keys come only after Carta reviews a production access request (typically 1-2 weeks).
Does the Carta API have rate limits?
Up to 10 requests/second and 300 requests/minute.
Can I connect Carta to my other tools without writing code against its API?
Yes. With Caddi you show the Carta task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Carta 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 Carta with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Carta is reviewed before it runs in production, and every run is logged.
Connect Carta without the build.
Drop your work email and pick a time. We'll show you Caddi running your Carta workflow end to end.