Administration on the command line
Administration runs through the program file itself. The commands execute before the web host and then exit — the running service does not have to be stopped for them.
cd "C:\Program Files\Invoiceflair\Portal"Invoiceflair.Api.exe <command> [arguments]The commands
Section titled “The commands”| Command | Purpose |
|---|---|
version |
version, build date, program path and the data root in use — where every support enquiry begins |
list-tenants |
the installation’s tenants: ID, plan, member count, creation date, name |
create-owner <email> --password <pw> [--must-change] |
create an account and its tenant (first access without a mail route) |
set-password <email> --password <pw> [--must-change] |
set the password of an existing account (support, emergencies, lifting a lockout) |
set-plan <tenantId|owner-email> <token> |
set a tenant’s plan. Every change appears in that tenant’s activity log |
create-key <name> [--monthly-limit N] |
create an API key — the plaintext appears once and cannot be recovered |
list-keys |
name, creation date, monthly limit, status. Never the secret |
disable-key <name> / enable-key <name> |
block or release; the service picks it up within 15 seconds without a restart |
delete-key <name> |
delete |
usage [--days N] [--key <name>] |
a usage report: total calls, success and failure, unique addresses, the distribution per tool and per key |
The trap that strikes silently
Section titled “The trap that strikes silently”On set-plan in an Enterprise installation
Section titled “On set-plan in an Enterprise installation”The plan limits do not apply there in any case; every tenant counts as unlimited. set-plan is
therefore mainly of interest for test setups and migrations back.
Related pages
Section titled “Related pages”| Topic | Page |
|---|---|
| the first account without a mail route | First run |
what usage reports on |
Monitoring |
| keys from a tenant’s perspective | API keys |