Inbound Rejections

Why You Would Use This

Rejections are inbound requests that failed ingest validation and were never forwarded. This page helps you separate security/configuration failures from downstream delivery failures.

Common causes:

• static token mismatch
• HMAC signature mismatch
• timestamp outside allowed window
• source IP outside allowlist

Console Workflow

1. Open Messages and select inbound direction.
2. Review the Rejections section.
3. Identify reason code and affected endpoint.
4. Fix provider configuration or endpoint verification rules.
5. Send a fresh provider test event to confirm recovery.

API Workflow

API reference: List inbound rejections

curl "https://api.hookbridge.io/v1/inbound-rejections?inbound_endpoint_id=YOUR_INBOUND_ENDPOINT_ID&limit=50" \
  -H "Authorization: Bearer YOUR_API_KEY"

The rejection log includes reason codes and details so you can quickly identify whether the issue is token, HMAC, IP policy, method, or another validation rule.

Remediation Checklist

• Verify provider secret/token values match endpoint config.
• Confirm provider timestamp behavior and clock skew.
• Confirm source IP ranges are current.
• Re-test with one known-good event.