Accounts
fakturownia-accounts
Fakturownia CLI accounts: create, inspect, delete, and unlink system accounts using the README-backed account contract, with sanitized structured output and optional profile persistence.
SKILL.md
Full skill instructions
Auto-generated by
go run ./cmd/gen-skills. Do not edit manually.
Accounts
PREREQUISITE: Read
fakturownia-sharedfirst.
Use This Skill When
- The task is about system-account creation, inspection, deletion, or unlinking partner-linked accounts.
- You need to work with the full top-level
accountrequest shape rather than the CLI's usual inner-object--inputcontract.
Covered Commands
fakturownia account create— Create a system account from the full upstream request objectfakturownia account get— Fetch current system-account metadatafakturownia account delete— Request deletion of the current system accountfakturownia account unlink— Unlink system accounts from a partner integration
Notable Flags
--input(required): Full account request JSON as inline JSON, @file, or - for stdin--save-as: Persist the returned credentials under this profile name--integration-token: Integration token used when requesting the current api_token--yes(required, defaultfalse): Confirm account deletion request--prefix(required): Account prefix to unlink; may be repeated or comma-separated
Environment
FAKTUROWNIA_PROFILE: Select a profile unless --profile is providedFAKTUROWNIA_URL: Override the base account URL from any profileFAKTUROWNIA_API_TOKEN: Override the API token from any profile
Output and Request Discovery
- Use
fakturownia schema account get --jsonto inspect sanitized account output fields such asprefix,url,login,email, andapi_token_present. - Use
fakturownia schema account create --jsonbefore building the full top-level account request object. - Unlike most CRUD nouns,
account createaccepts the full upstream request object, including top-levelaccount,user,company, and optionalintegration_token. - Structured output is sanitized and omits the raw returned API token; use
--rawonly when you explicitly need the exact upstream response.
Examples
fakturownia account create --input '{"account":{"prefix":"acme"},"user":{"login":"owner","email":"[email protected]","password":"secret"},"company":{"name":"Acme"}}' --json
fakturownia account create --input @account-create.json --save-as acme
fakturownia account create --input @account-create.json --dry-run --json
fakturownia account get --json
fakturownia account get --integration-token PARTNER_TOKEN
fakturownia account get --raw
fakturownia account delete --yes --json
fakturownia account delete --yes --dry-run --json
fakturownia account unlink --prefix acme --json
fakturownia account unlink --prefix acme --prefix beta --integration-token PARTNER_TOKEN
fakturownia account unlink --prefix acme,beta --dry-run --json
