Skip to main content
Use the Fintoc CLI to make API requests, trigger test events, and forward webhooks to your local server.

Available resources

Every command follows the pattern fintoc <resource> <action> [flags]. The CLI supports these resources and actions:

Make an API request

The general form is fintoc <resource> <action> [flags]. Run fintoc --help to list available resources. Run fintoc <resource> --help to list the resource’s actions.
Use --json for machine-readable output:
v2 transfers create requires a JSON Web Signature (JWS) private key for signing. Provide it via the --jws-private-key flag or set jws_private_key in ~/.fintoc/config.toml. To generate a key pair, see Generate JWS Keys.

Pass a JSON payload

For create commands, pass a payload file with --from-json, or pipe one in with -:
You can mix flags with --from-json. Flag values take precedence over JSON keys. The CLI merges nested objects but replaces entire arrays.

Delete a resource

Delete commands ask for confirmation before removing the resource. Pass --yes to skip the prompt in automated environments.

Trigger test events

fintoc trigger generates a test event for your account. The event exercises your webhook handlers without producing real activity.
--override accepts dot notation (metadata.order_id=abc123). You can repeat the flag. The same precedence rules as --from-json apply.

Listen to webhooks on localhost

fintoc webhooks listen opens a WebSocket connection to Fintoc and forwards events to your local server. The CLI signs each forwarded request. You can use your existing signature verification without a public tunnel.
Filter by event type: