Caraer CLI
The Caraer CLI (caraer-cli) is the downloadable developer tool for managing
Caraer apps, webhooks, serverless functions, schedules, inbound routes, and
local developer projects.
Install
Section titled “Install”pipx install caraer-cli# or from a local checkout:pip install -e ".[dev]"Core workflows
Section titled “Core workflows”caraer auth login --email you@example.comcaraer company select <company-uuid>caraer apps init --label "My Sync App"cd my_sync_appcaraer apps add function sync-handlercaraer apps add schedule renew-watch --function sync-handlercaraer apps add inbound provider-push --function sync-handlercaraer apps pushcaraer apps local logscaraer apps local devcaraer sandbox create --name my-sandboxDeveloper project mutations require the app creator company (or super-admin). Knowing an app UUID alone is not authorization.
Typed serverless payloads live in the Caraer clients (@caraer/client /
caraer-client).
Inspect and resume webhook deliveries
Section titled “Inspect and resume webhook deliveries”CLI 0.1.12+ exposes automatic deactivation for the selected company’s webhooks:
caraer company select <company-uuid>caraer webhooks list --app <app-uuid>caraer webhooks show <webhook-uuid> --app <app-uuid>After fixing and testing the destination, explicitly resume future deliveries with the same app-resource edit permissions used to edit the webhook:
caraer webhooks reactivate <webhook-uuid> --app <app-uuid>caraer webhooks show <webhook-uuid> --app <app-uuid>Expect deactivated: false and failureCount: 0. Only the selected company’s
subscription resumes; old queued events are not replayed. Tests and project
pushes preserve automatic deactivation. See webhook recovery
for failure thresholds, status fields, and verification with a new sandbox event.
Related
Section titled “Related”- Tutorial: How to create a Caraer app
- Serverless functions in Caraer apps
- Source:
caraer-clirepository - Platform APIs: Caraer Java Backend (
/api/v2/apps, installation runtime, developer-projects) - Runtimes:
nodejs22,python312on Google Cloud Functions (V2: one container per app)