Karbon integration
Built for Karbon firms.
Reckonry connects directly to your Karbon tenant and turns the data already in it into a per-client view of profit, cost, and unbilled work. No middleware. No third-party broker. Read-only in practice.
How it connects
Three things to know before you connect.
Direct
No middleware between us and Karbon.
Reckonry calls Karbon’s public API directly from our Google Cloud Run service. There is no third-party broker, no integration platform, and no shared connector pool in between.
Encrypted
Secure in transit and at rest.
All Karbon traffic runs over TLS. Your Karbon credentials and the data we pull are encrypted at rest. Full controls are documented on our security page.
Read-only in practice
We never write to Karbon.
Karbon’s API keys are read-write by default — the platform doesn’t currently offer a read-only key. Our application never issues a write call. Details below.
Read-only, concretely
The write code paths don’t exist in our codebase.
Karbon issues a single key class that grants both read and write capability. We use that key only to read. The way we make that concrete is structural, not a policy promise:
- No callsite anywhere in our application invokes POST, PUT, PATCH, or DELETE against any Karbon endpoint.
- The internal helpers a developer would have to call to issue a write request to Karbon — create, update, delete — are not present.
- Adding write capability would mean shipping new code, going through review, and changing the surface of the service. It isn’t something an operator could enable from a settings page.
You can rotate or revoke your Karbon AccessKey and Bearer token in Karbon at any time. Doing so stops Reckonry from syncing on the next attempt and leaves the data already pulled intact in your Reckonry tenant.
Coming soon
Connect Karbon, see your real margins.
Reckonry isn’t open yet. At launch: seven days free, no credit card to begin. Generate your AccessKey and Bearer token inside Karbon under Settings → Developer, paste both into Reckonry, and your tenant starts syncing.