Publishing your app
From a free developer account to a published integration — sign up, make your first API call, register an OAuth app, confirm your domain, and publish.
This walkthrough takes you from nothing to a publish-ready ClientCasa integration. It's free — developer accounts cost nothing and never expire.
Create a developer account
Sign up at /developers/signup with your email, verify it, and tell us what you're building. You land in the developer dashboard. This account is a sandbox: payments run in Stripe test mode, email is captured to your in-app inbox, and PDFs are watermarked — see Developer accounts for the full picture.
Make your first API call
In Settings → Advanced → API keys, create a key and call the API:
curl https://app.clientcasa.com/v1/clients \
-H "Authorization: Bearer YOUR_API_KEY"That's a system-to-system call against your own data. See Authentication for the full auth model.
Register an OAuth app
If other ClientCasa businesses will connect your product, register an OAuth app in Settings → Advanced → OAuth apps. You get a client_id and client_secret; set your redirect URIs and the scopes you need. Round-trip the authorization-code flow and you'll see the consent screen your customers will see.
Request only the scopes you actually need. The consent screen shows users exactly what you ask for, and a tighter request earns more trust.
Confirm your domain
Open your app's Manage page and enter the domain your product lives on. Add the TXT record we show you at _clientcasa-challenge.{your-domain}, then click Check now. Once it resolves, your consent screen shows Domain confirmed: {your-domain} — the only trust signal ClientCasa issues. We don't review your app; we confirm you control the domain.
Complete your public listing
Fill in your category, a one-line tagline, a description, your support email, and your privacy policy and terms of service URLs. These are shown to end users as-is on the consent screen and in the directory. We periodically re-check that the domain TXT record and those URLs stay reachable.
Accept the agreement and publish
Read and accept the Developer App Agreement. With your domain confirmed, your listing complete, and the agreement accepted, click Publish. Your app becomes connectable by any ClientCasa organization and appears in the integrations directory.
Publishing is opening soon — the agreement is being finalized. Everything up to this step works today, so you can be fully prepared.
After you publish
- Your
client_idis permanent. Unpublishing or transferring the app keeps it — existing customer connections never break. - Keep your URLs live. If your domain TXT record or privacy/terms URLs go unreachable, we notify you and give a 14-day grace before reverting the app to draft (the
client_idis never revoked for this). - Transferring ownership? See ownership transfer.
OAuth quick-start with PKCE
End-to-end authorization-code-with-PKCE flow against the ClientCasa OAuth provider. Copy-pasteable Node.js example, ~50 lines.
Webhook receiver with HMAC verification
Build a webhook receiver that verifies HMAC-SHA256 signatures, rejects replays, dedupes by event ID, and handles retries. Works on Node, Edge runtimes, and Cloudflare Workers.