Know what connects. And what does not.
Structured imports, practical exports, Google sign-in, and Enterprise-scoped SSO. No self-serve public API, webhooks, or app marketplace today.
One page for the status of every connection.
“Integration” can mean login, import, export, live synchronization, or a custom implementation. This table keeps those categories separate.
Move the record without locking it inside the platform.
Use CSV workflows for historical registers, bulk issuances, bulk transfers, and portfolio migration preparation.
- Up to 10,000 rows
- Server-side processing
- Post-import reconciliation
Export cap table data as CSV and selected audit activity in machine-readable form when the plan supports it.
- Cap table CSV
- Activity-log CSV on eligible plans
- Standard data portability
Export corporate documents in Word or PDF and create plan-dependent cap table PDFs or compliance dossiers.
- Word and PDF documents
- Cap table PDFs
- Diligence packages
Give stakeholders access through Equity Vault or share verification and scenario links where the plan allows.
- Stakeholder holdings view
- QR certificate verification
- Revocable scenario links
File-based migration, not a hidden live sync.
Octelligence can receive exports from common cap table platforms and spreadsheets, then combine them with corporate documents. The process is snapshot, map, import, reconcile, and cut over. It is not continuous two-way synchronization.
A connector can make bad source data move faster. Migration still needs field mapping, historical evidence, total reconciliation, exception ownership, and a deliberate cutover. Octelligence does not describe that work as an automatic sync.
- A dated snapshot of the source system
- A record of field and transaction mappings
- An exception log for missing or contradictory evidence
- Reconciliation and stakeholder cutover approval
Scope the operating requirement before naming the connector.
Enterprise includes the ability to scope SSO and custom integrations. Feasibility, implementation, security review, responsibilities, and pricing depend on the specific requirement.
- Which system needs to exchange data with Octelligence?
- Is the flow inbound, outbound, or bidirectional?
- Which records and events need to move, and how often?
- What authentication, audit, residency, and approval controls apply?
- Who owns source-data quality, exceptions, testing, and cutover?
One internal API powers the product. It is not a public developer API.
Ledger and Equity Vault use one backend so corporate records and stakeholder views read from the same data. Customers do not currently receive API credentials, public documentation, or webhook configuration.
There is no published availability date. If an API or event requirement affects your buying decision, tell us the objects, actions, volume, and security model you need.
No self-serve API keys
No public developer documentation
No public webhooks
No Zapier connector
Integration and API questions
Tell us the system, data, frequency, and controls involved. We will tell you whether it fits the current product, an Enterprise scope, or neither.