CLI Destination

When to use this destination type

Choose CLI when the receiver target is Authenticated fasthook-cli tunnel. Destinations are outbound delivery targets: they do not decide whether a source request should be accepted, and they do not own connection filters or transformations. They own where the final delivery goes and how FastHook should authenticate, pace, disable, and inspect that delivery.

A destination can be reused by multiple connections when several source branches should feed the same receiver. Reuse keeps receiver capacity, credentials, and attempt evidence attached to one destination id.

FastHook dashboard fields

In the dashboard, create a destination, set Destination Type to CLI, then fill the fields below.

API config fields

The REST API stores destination-specific behavior under config. Use PATCH for focused edits and PUT only when your request contains the full config you want to keep.

{
  "name": "local-orders-api",
  "type": "CLI",
  "config": {
    "path": "/webhooks/orders",
    "http_method": "POST",
    "rate_limit": 10,
    "rate_limit_period": "second"
  }
}

curl -X POST "https://api.fasthook.io/v1/destinations" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "local-orders-api",
  "type": "CLI",
  "config": {
    "path": "/webhooks/orders",
    "http_method": "POST",
    "rate_limit": 10,
    "rate_limit_period": "second"
  }
}'

Authentication

Destination authentication is outbound. It helps the receiver trust or accept FastHook delivery, and it is separate from source authentication that verifies the original webhook producer.

• Authenticated FastHook CLI tunnel session

HTTP methods and rate limit

This destination type uses the methods below for delivery attempts. Rate limits apply at the destination boundary, so every connection that targets the same destination shares that capacity.

Rate limit: Optional. Useful when replaying many events into a local service.

Delivery behavior

• A CLI destination does not store localhost host or port. The active CLI command supplies the local target with --to.
• FastHook delivers the event to the tunnel service, and the authenticated CLI session forwards it to the local receiver.
• The CLI sends local response status, headers, body, and errors back so FastHook can store attempt evidence.
• More than one CLI can connect to the same destination, but separate destinations are easier to reason about for separate developers.

Setup checklist

1. Create a destination and choose CLI as the destination type.
2. Optionally set a CLI path. Leave it blank to use /.
3. Create or edit a connection so accepted source events route to the CLI destination.
4. Log in with fasthook-cli and start a tunnel with fasthook tunnel --destination des_xxx --to 8080.
5. Send or replay events and inspect the local receiver response in FastHook attempts.

Troubleshooting

Related docs

• Destinations
• CLI and tunneling
• Test webhooks locally
• CLI connection management
• API reference