CLI

The Hilt CLI is for teams that want fast terminal workflows around the same objects the dashboard already uses. It is a public Hilt surface across the plan ladder, not a higher-tier add-on.

What the CLI is best at

Use it when you want:

quick merchant lookups from a terminal
repeatable support and operations scripts
webhook endpoint and delivery control without opening the dashboard
receipt proof and recurring recovery actions from one terminal flow
sandbox session testing before live traffic

Install from Hilt

npm install -g https://www.hilt.so/downloads/hilt-cli-latest.tgz

If you want a pinned version instead of latest, install the versioned tarball:

npm install -g https://www.hilt.so/downloads/hilt-cli-1.0.0.tgz

Verify the package checksum

curl -O https://www.hilt.so/downloads/hilt-cli-1.0.0.tgz
curl -O https://www.hilt.so/downloads/hilt-cli-1.0.0.tgz.sha256
sha256sum -c hilt-cli-1.0.0.tgz.sha256

Authentication commands

hilt login
hilt login --email merchant@example.com
hilt login --token EXISTING_TOKEN
hilt whoami
hilt logout

Key management

hilt keys list
hilt keys create --name "Production integration"
hilt keys create --name "Sandbox checks" --sandbox
hilt keys revoke KEY_ID

Sandbox keys do not create a fake settlement rail. They are best used for:

lower-risk pre-launch tooling
sandbox session testing
pre-launch automation inside a real merchant workspace

Webhook commands

hilt webhooks list
hilt webhooks create --label "Prod endpoint" --url https://example.com/hilt --event payment.confirmed
hilt webhooks test ENDPOINT_ID --event payment.confirmed
hilt webhooks deliveries --status dead_letter
hilt webhooks replay DELIVERY_ID
hilt webhooks events --type receipt.created
hilt webhooks timeline --payment PAYMENT_ID

Best use

create and inspect endpoints
send signed test events
read delivery status
re-send retry-scheduled or dead-letter deliveries
inspect the event timeline for a payment or membership

Sandbox commands

hilt testing scenarios
hilt testing run --scenario confirmed_access --product PRODUCT_ID
hilt testing run --scenario delivery_failed --product PRODUCT_ID
hilt testing list
hilt testing get SESSION_ID

Use this when you want to validate:

webhook consumers
SDK or Postman object handling
delivery-failure recovery
recurring grace handling

Then use setup readiness and, when useful, an optional low-value live settlement check before real launch.

Product commands

hilt pay products list
hilt pay products list --status ACTIVE
hilt pay products get PRODUCT_ID
hilt pay products archive PRODUCT_ID

Membership commands

hilt pay members list
hilt pay members lookup --wallet WALLET_ADDRESS
hilt pay members get MEMBERSHIP_ID
hilt pay members renewal-intelligence --window-days 14
hilt pay members retry-delivery MEMBERSHIP_ID
hilt pay members delivery-diagnostics MEMBERSHIP_ID
hilt pay members delivery-support-ticket MEMBERSHIP_ID

Best use

recurring cohort visibility
subscription and expiry visibility
Telegram or Discord diagnostics
support-linked delivery recovery

Receipt commands

hilt pay receipts list
hilt pay receipts list --product PRODUCT_ID --query invoice
hilt pay receipts get RECEIPT_ID
hilt pay receipts send-proof RECEIPT_ID --email buyer@example.com

Best use

receipt search
proof retrieval
direct proof sharing from terminal workflows

Useful flags

--json for raw JSON output on data commands
-h, --help for command help
-v, --version for version output

Command-to-route map

CLI command	API route
`hilt keys list`	`GET /v1/keys`
`hilt keys create`	`POST /v1/keys`
`hilt keys revoke`	`DELETE /v1/keys/{key_id}`
`hilt webhooks list`	`GET /v1/webhooks/endpoints`
`hilt webhooks create`	`POST /v1/webhooks/endpoints`
`hilt webhooks test`	`POST /v1/webhooks/endpoints/{endpoint_id}/test`
`hilt webhooks deliveries`	`GET /v1/webhooks/deliveries`
`hilt webhooks replay`	`POST /v1/webhooks/deliveries/{delivery_id}/replay`
`hilt webhooks events`	`GET /v1/webhooks/events`
`hilt webhooks timeline`	`GET /v1/webhooks/timeline`
`hilt testing scenarios`	`GET /v1/testing/scenarios`
`hilt testing run`	`POST /v1/testing/sessions`
`hilt testing list`	`GET /v1/testing/sessions`
`hilt testing get`	`GET /v1/testing/sessions/{session_id}`
`hilt pay products list`	`GET /v1/products`
`hilt pay products get`	`GET /v1/products/{product_id}`
`hilt pay products archive`	`DELETE /v1/products/{product_id}`
`hilt pay members list`	`GET /v1/memberships`
`hilt pay members lookup`	`GET /v1/memberships/lookup`
`hilt pay members get`	`GET /v1/memberships/{membership_id}`
`hilt pay members renewal-intelligence`	`GET /v1/memberships/renewal-intelligence`
`hilt pay members retry-delivery`	`POST /v1/memberships/{membership_id}/retry-delivery`
`hilt pay members delivery-diagnostics`	`GET /v1/memberships/{membership_id}/delivery-diagnostics`
`hilt pay members delivery-support-ticket`	`POST /v1/memberships/{membership_id}/delivery-support-ticket`
`hilt pay receipts list`	`GET /v1/receipts`
`hilt pay receipts get`	`GET /v1/receipt/{receipt_id}`
`hilt pay receipts send-proof`	`POST /v1/receipt/{receipt_id}/send-proof`

A reliable support flow in the terminal

hilt pay members lookup --identity @buyer
hilt pay members delivery-diagnostics MEMBERSHIP_ID
hilt pay members retry-delivery MEMBERSHIP_ID
hilt pay receipts send-proof RECEIPT_ID --email buyer@example.com

That sequence usually gets you from buyer problem to concrete action quickly.

Common questions

What is the Hilt CLI for?

The CLI is for repeatable merchant and developer operations from a terminal: API keys, webhooks, testing, products, members, receipts, proof, and support recovery.

Is the CLI only for higher plans?

No. The CLI is a public Hilt surface across the plan ladder. Higher plans mainly change fees, support level, and operating comfort.

When is CLI better than the dashboard?

Use the CLI for repeatable support workflows, terminal lookups, JSON output, scripts, and quick operational checks. Use the dashboard for normal merchant setup and daily visual operations.

Start here

After payment

Examples and reference

CLI

CLI

What the CLI is best at

Install from Hilt

Verify the package checksum

Authentication commands

Key management

Webhook commands

Best use

Sandbox commands

Product commands

Membership commands

Best use

Receipt commands

Best use

Useful flags

Command-to-route map

A reliable support flow in the terminal

Common questions

What is the Hilt CLI for?

Is the CLI only for higher plans?

When is CLI better than the dashboard?

​CLI

​What the CLI is best at

​Install from Hilt

​Verify the package checksum

​Authentication commands

​Key management

​Webhook commands

​Best use

​Sandbox commands

​Product commands

​Membership commands

​Best use

​Receipt commands

​Best use

​Useful flags

​Command-to-route map

​A reliable support flow in the terminal

​Common questions

​What is the Hilt CLI for?

​Is the CLI only for higher plans?

​When is CLI better than the dashboard?

CLI

What the CLI is best at

Install from Hilt

Verify the package checksum

Authentication commands

Key management

Webhook commands

Best use

Sandbox commands

Product commands

Membership commands

Best use

Receipt commands

Best use

Useful flags

Command-to-route map

A reliable support flow in the terminal

Common questions

What is the Hilt CLI for?

Is the CLI only for higher plans?

When is CLI better than the dashboard?