CLI Guide — dodil appid
All of AppID drives from the unified Dodil CLI . Sign in once with dodil auth login; every dodil appid command then acts in your organization — there is no --org flag, the platform derives it from your session.
dodil appid health # is the service up
dodil appid pool list # what pools do I haveConventions
- Output: human tables by default;
-o jsonfor scripting (camelCase fields, same shapes as the REST API). - JSON-document flags (
--policies,--settings,--branding,--role-catalog,--config,--metadata) accept inline JSON,@file, or-for stdin. - Destructive commands (
pool delete,user delete --hard,user-store reset,connection remove) require--yes. - Persistent flags:
--api-endpoint,--token,--debug,-o/--output.
Command groups
| Group | Covers | Page |
|---|---|---|
pool, settings, branding, roles, connection | Create and configure pools; run the test flow | Pools & configuration |
user, tenant | App users, invitations, bans, tenants and memberships | Users & tenants |
user-store | Choose and migrate where users live | User stores |
The five-minute path
dodil appid pool create my-app --with-local
dodil appid settings set my-app --redirect-uris "https://app.example.com/callback"
dodil appid user create my-app [email protected] --password 'S3curePass!'
dodil appid pool test-flow my-app [email protected] 'S3curePass!' \
--redirect-uri https://app.example.com/callbackSee the Quickstart for the annotated version.