Recognize that Carta does not offer a general-purpose public REST API for cap table or equity data; API access is gated by partnership agreements and is not available to arbitrary third parties — verify your access tier before planning an integration.
For enterprise customers with negotiated API access, authenticate using OAuth 2.0 or API tokens as specified in the Carta partner documentation provided during onboarding.
For user lifecycle management (provisioning and deprovisioning), Carta supports SCIM 2.0 — enable it under Carta Settings > Security > SCIM and generate a SCIM bearer token.
Configure your identity provider (Okta, Azure AD, etc.) to point to Carta's SCIM base URL and use the generated bearer token; Carta's SCIM implementation supports Users and Groups (mapping to Carta stakeholder groups).
SCIM provisioning handles account creation, attribute updates, and deactivation; it does not expose equity, vesting schedules, or cap table data — those require the partner API if available.
For data exports (409A valuations, cap table snapshots), use Carta's built-in CSV export features in the UI as the reliable fallback when API access is unavailable.
Known gotchas
Carta's API is not self-serve and does not have a public developer portal; teams that build integrations assuming open API access frequently discover mid-project that they need a partnership agreement — confirm access in writing before scoping engineering work.
SCIM attribute mapping is strict; Carta requires specific SCIM schema attributes and may ignore or reject custom extension attributes not listed in their documentation — test provisioning with a single user before bulk-enabling.
Carta has historically changed its product architecture through acquisitions and product updates; integration patterns that worked previously may require re-verification against current documentation.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp