Developer accounts

A developer account is a free-forever ClientCasa organization built for integrators. It gives you full access to the developer surfaces — API keys, OAuth apps, and webhooks — without a subscription, a trial countdown, or a card on file. It's the right home for a long-lived OAuth client_id that your customers' integrations depend on.

Sign up

Create one at /developers/signup. It's the same secure signup as a customer account (email verification, bot and disposable-email protection), then a short step where you tell us what you're building.

The persistence contract

Your OAuth client_id is a public identifier embedded in your code and in every customer who has connected your app. Once you publish an app, your developer account is not touched by routine operations — billing cleanup, trial expiry, or inactivity sweeps will never disable a published app's client_id. We only disable an app deliberately and for cause (abuse, a Developer App Agreement violation, or legal compulsion), and such actions are logged.

This is the one promise the platform makes, and it's deliberately narrow: it keeps the integrations your customers rely on from disappearing.

What a developer account is not

A developer account is a sandbox for building and testing — not for running a real business. So you're never surprised later:

• Payments run in Stripe test mode only. Connect a test Stripe account and run the full charge → webhook loop with test cards. Real money is impossible.
• Email is sandboxed. Outbound email (invoices, receipts, notifications) is captured to your in-app developer inbox instead of being delivered, so you can inspect exactly what would have been sent. Webhook test deliveries are the exception — those fire for real.
• Generated PDFs are watermarked "developer org — not for production use."
• Record limits keep it a sandbox: roughly 25 clients, 25 invoices, 100 contacts (and similar). Need more for a legitimate reason? Email support and we can raise them.

Domain-confirmed publishing

ClientCasa does not review, audit, or endorse third-party apps. The one thing we verify is mechanical: that you control the DNS for the domain your app is associated with.

1. In your OAuth app's settings, open Manage and enter your domain.
2. Add the TXT record we show you at _clientcasa-challenge.{domain}.
3. Click Check now. On success, the app shows Domain confirmed: {domain} — the only platform-issued signal an end user sees on the consent screen.

To publish, you also fill a public listing (category, tagline, description, support email, privacy + terms URLs) and accept the Developer App Agreement. When all three are in place, publishing makes your app connectable by any ClientCasa organization and listed in the integrations directory. Your client_id never changes — unpublishing later keeps existing connections working.

Ownership transfer

You can hand an app to another developer organization — for an acquisition, a team change, or a hand-off:

1. On the app, open Transfer ownership and enter the new owner's email (they must already have a developer account).
2. They receive a link and accept within 24 hours.

The client_id is invariant across transfers, so customer connections are preserved — nothing breaks for the businesses already using your app.

Next

• Publishing your app — a walkthrough
• OAuth Apps reference
• Connecting third-party apps safely (the end-user view)