Developers
Build on Alethia
A workspace-scoped REST API over the same entities, people, deals, documents, properties, fund commitments and cap-table records the app runs on — plus outbound webhooks for the events that matter. Authenticate with a workspace API key and start building.
- 9
- Resources
- 39
- Endpoints
- 19
- Webhook events
- 1000
- Requests / 15 min
Quick start
From zero to your first request
Two steps: mint a workspace API key, then call the API with it as a bearer token.
- 1
Create an API key
As a workspace admin on the Enterprise plan, open Settings → Integrations and choose New key. Give it a label, at least one scope (
read,write) and — only if the integration needs them — therestricted_recordsormanage_webhookscapabilities. The plaintext key is shown once; store it securely. - 2
Make your first request
Send the key as a bearer token in the
Authorizationheader on every call. The workspace is resolved from the key itself — there is no separate workspace parameter to pass.
curl "https://app.alethiahq.com/api/v1/entities" \
-H "Authorization: Bearer tk_{workspaceId}_{secret}"Reference
Everything you need to integrate
Authentication, every resource and endpoint, webhooks, and the error and rate-limit contract — plus a downloadable OpenAPI document.
Start here
Authentication
How to mint a workspace API key, the Authorization header format, scopes, capabilities and plan requirements.
Read more →Reference
Resources
Every resource and all 39 endpoints — parameters, request/response fields and a curl example for each.
Read more →Events
Webhooks
Subscribable events, payload shapes, HMAC signature verification, delivery and retries, and the test endpoint.
Read more →Contract
Errors & limits
The error envelope, every status code the API returns, rate limits and cursor pagination.
Read more →Machine-readable
OpenAPI specification
The whole API as an OpenAPI 3.0 document — paths, schemas, security and the webhook event catalogue.
Open the spec ↗Questions
Building on the API, answered
Do I need a paid plan to use the API?
The public API is an Enterprise capability: the workspace subscription must be active on Enterprise (verifyApiKey returns 403 otherwise), and workspace/company access must not be suspended. Scopes and any high-trust capabilities are set when the key is minted, in-app.
Where do I create an API key?
In the app, as a workspace admin: Settings → Integrations → New key. Choose a label and at least one scope; the plaintext key is shown once and cannot be retrieved again.
What's the rate limit?
1000 requests per 15 minutes, per key. Exceeding it returns 429 with Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset headers.
Is there a machine-readable spec?
Yes — the full OpenAPI 3.0 document is served at /api/openapi.json, unauthenticated, ready to import into Postman, Swagger UI or a codegen tool.
Which resources are read-only over the API?
Properties and fund commitments are list/read (GET) only — there is no create, update or delete route for either.
Talk to us about your integration
Tell us what you're building — CRM sync, a reporting pipeline, an internal tool — and we'll walk through the resources and events that fit.