Rehook
HomePricingLog in

Developer Docs

Routes

Routes decide where incoming source events get delivered.

Route anatomy

  • - Destination URL
  • - Match conditions (header, JSON path, regex)
  • - Priority and enabled state
  • - Retry and timeout controls

Typical setup

  1. 1. Start with one broad route to your dev endpoint.
  2. 2. Add specific routes for event subsets as needed.
  3. 3. Use priorities so specific routes win first.
  4. 4. Keep retries enabled for transient failures.

Routing modes

  • - Single Target: deliver to the first matched route only.
  • - Match All: deliver to every matched route.
  • - Match order is by ascending priority (lower number first).
  • - Routes with no conditions always match; routes with conditions require all conditions to pass.
  • - Use unique priorities in Single Target mode to avoid tie-order ambiguity.

Best practice

Prefer explicit conditions over catch-all routing once your event volume grows. It keeps debugging fast and makes delivery behavior predictable for teams.