Skip to content
LiveNew tools this week
Submit
AIMarketly
fakturownia-webhooks logo

Webhooks

fakturownia-webhooks

Fakturownia CLI webhooks: list, fetch, create, update, and delete webhooks using conservative README-backed request and output discovery.

sixers/fakturownia-cli0installs0starsFinance & Trading

SKILL.md

Full skill instructions

Auto-generated by go run ./​cmd/​gen-skills. Do not edit manually.

Webhooks

PREREQUISITE: Read fakturownia-shared first.

Use This Skill When

  • The task is about reading or mutating webhooks.
  • You need the conservative webhook kind, url, api_token, and active request contract without inventing undocumented wrapper keys.

Covered Commands

  • fakturownia webhook list — List webhooks
  • fakturownia webhook get — Fetch a single webhook by ID
  • fakturownia webhook create — Create a webhook from the full top-level request object
  • fakturownia webhook update — Update a webhook from the full top-level request object
  • fakturownia webhook delete — Delete a webhook

Notable Flags

  • --page (default 1): Requested result page
  • --per-page (default 25): Requested result count per page
  • --id (required): Webhook ID
  • --input (required): Full webhook request JSON as inline JSON, @file, or - for stdin
  • --yes (required, default false): Confirm webhook deletion

Environment

  • FAKTUROWNIA_PROFILE: Select a profile unless --profile is provided
  • FAKTUROWNIA_URL: Override the base account URL from any profile
  • FAKTUROWNIA_API_TOKEN: Override the API token from any profile

Output and Request Discovery

  • Use fakturownia schema webhook list --json and fakturownia schema webhook get --json before building selectors.
  • Read output.known_fields to discover conservative webhook fields such as kind, url, api_token, active, created_at, and updated_at.
  • Use fakturownia schema webhook create --json and fakturownia schema webhook update --json to inspect request_body_schema before building webhook payloads.
  • Unlike most CRUD nouns, webhook create and update accept the full top-level request object because the direct README documents endpoints but not a wrapper key.
  • Start from the curated kind values in schema output and keep the payload conservative rather than inventing undocumented fields.

Examples

fakturownia webhook list --json
fakturownia webhook list --columns id,kind,url,active
fakturownia webhook list --page 2 --per-page 25 --raw
fakturownia webhook get --id 7
fakturownia webhook get --id 7 --fields id,kind,url,active --json
fakturownia webhook get --id 7 --raw
fakturownia webhook create --input '{"kind":"invoice:create","url":"https://example.com/hook","api_token":"secret","active":true}' --json
fakturownia webhook create --input @webhook.json
fakturownia webhook create --input '{"kind":"invoice:create","url":"https://example.com/hook"}' --dry-run --json
fakturownia webhook update --id 7 --input '{"active":false}' --json
fakturownia webhook update --id 7 --input @webhook-update.json
fakturownia webhook update --id 7 --input '{"url":"https://example.com/hook"}' --dry-run --json
fakturownia webhook delete --id 7 --yes --json
fakturownia webhook delete --id 7 --yes --dry-run --json

Related Skills