Skip to main content

Project Settings

The Settings page lets you configure project-level options, manage API keys, and control access.

General Settings​

Project Name​

Update the display name of your project.

Header Prefix​

Set a custom prefix for outgoing headers. Dispatch adds these headers to delivery requests:

  • X-{prefix}-Event-ID — the event UUID
  • X-{prefix}-Endpoint-ID — the endpoint UUID

Default prefix: dispatch

API Keys​

API keys provide programmatic access to your project's webhook endpoints without HMAC signatures.

Creating an API Key​

  1. Click Create API Key
  2. Enter a descriptive name
  3. The key is displayed once — copy it immediately

Key format: dsp_<random-string>

Using API Keys​

Include the key in the Authorization header when sending webhooks:

curl -X POST https://api.dispatch.tech/hooks/my-slug \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer dsp_your-key-here" \
  -d '{"event": "test"}'

Revoking an API Key​

Click Revoke next to any active key. Revoked keys are immediately invalid and cannot be restored.

Security​

  • Keys are stored securely — the raw key is never stored after creation
  • Only the dsp_ prefix is visible after creation
  • Revoked keys show the revocation timestamp

Privacy Settings​

On paid plans, you can make a project private:

  1. Toggle the Private switch
  2. Add members from your organization who should have access
  3. Assign roles: admin, developer, or viewer

Organization owners and admins always have access to all projects.

Issue Notifications​

Issue notifications alert you when something goes wrong with your webhooks — delivery failures or source processing errors.

Enable / Disable​

Use the Issue Notifications toggle to turn notifications on or off for the entire project. When off, no notifications are sent regardless of any configured rules.

Notification Rules​

When notifications are enabled, you can configure rules in two sections:

Delivery rules — fire when a destination fails to receive an event.

Source error rules — fire when an incoming webhook has a processing error, such as an invalid signature, invalid API key, or malformed JSON body.

Each rule lets you configure:

  • Scope — target all destinations/sources, specific ones by name, or a name pattern (e.g. Discord*)
  • Notify via — send an email to project members, deliver to one or more destinations, or both
  • Conditions (optional) — only fire the notification when the event payload or headers match specific criteria

For delivery rules, you also choose when to notify:

  • First failure — immediately on the first failed attempt
  • After N retries — after a specific retry number
  • Final attempt — once all retry attempts are exhausted

Dispatch deduplicates notifications so you won't receive repeated alerts for the same ongoing issue.

Permissions​

Org developers, admins, and owners can create, edit, and delete notification rules.

Danger Zone​

Archive Project​

Archiving a project:

  • The project no longer appears in listings
  • Endpoint URLs return 404
  • Event and delivery history is preserved