Destination type

Mock API Destination

Use mock API destinations when you need a disposable receiver for route tests, demos, examples, screenshots, or safe delivery validation before a real consumer exists.

MOCK_APIFastHook mock receiverPOST, PUT, PATCH, DELETETesting
All destination typesDestinations docs
Mock API destination delivery flowFastHook routes accepted events through a connection to a Mock API destination and stores delivery attempt evidence.AcceptedRequestsource verifiedConnectionRoute branchfilters and transformsretry policyMOCK_APIMock APIFastHook mock receiverPOST, PUT, PATCH, DELETEAttemptEvidencestatus + bodyDestination config owns target, auth, method, rate limit, disabled state, and delivery attempt evidence.
For mock destinations, FastHook uses the same request, event, and attempt model while targeting a safe fixed receiver.

When to use this destination type

Choose MOCK_API when the receiver target is FastHook mock receiver. 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 MOCK_API, then fill the fields below.

Mock API URL

Read-only endpoint set to https://mock.fasthook.io/.

HTTP method

Method used when delivering to the mock endpoint.

Max delivery rate

Optional pacing for test traffic.

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.

config.url

Fixed mock receiver URL: https://mock.fasthook.io/.

config.http_method

Outbound method used for the mock delivery attempt.

config.rate_limit

Optional pacing limit for mock deliveries.

config.rate_limit_period

Rate-limit period: second, minute, or hour.

Mock API destination config
{
  "name": "mock-delivery-target",
  "type": "MOCK_API",
  "config": {
    "url": "https://mock.fasthook.io/",
    "http_method": "POST"
  }
}
Create Mock API destination with cURL
curl -X POST "https://api.fasthook.io/v1/destinations" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "mock-delivery-target",
  "type": "MOCK_API",
  "config": {
    "url": "https://mock.fasthook.io/",
    "http_method": "POST"
  }
}'

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.

  • No destination auth

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.

POSTPUTPATCHDELETE

Rate limit: Optional. Useful for shaping demos and replay tests.

Delivery behavior

  • The mock endpoint gives you a controlled target without configuring a production receiver.
  • Mock destinations are useful for testing source auth, filters, transformations, retries, and metrics without external side effects.
  • Because the endpoint is fixed, edits focus on name, method, status, and optional rate limit.

Setup checklist

  1. Create a destination and choose MOCK_API as the destination type.
  2. Keep the fixed mock URL.
  3. Choose the method you want FastHook to use in the delivery attempt.
  4. Connect a source to the mock destination and send a test event.
  5. Inspect request, event, and attempt evidence before switching the connection to a real receiver.

Troubleshooting

Mock attempts do not appear.

Confirm the connection targets the mock destination and that the source request was accepted.

A test route later hits production.

Keep mock, staging, and production destinations separate and review connection destination_id before replaying traffic.

The mock target is not editable.

That is expected. Use HTTP when you need a custom receiver URL.

Related docs