Create and manage subscriptions

Open Webhooks from your Quire account menu. Every active team member can create subscriptions. Members manage their own subscriptions; team owners can view and manage every subscription in the team.

Configure a subscription

Provide a descriptive name and a public HTTPS endpoint. Quire accepts only port 443, rejects credentials and fragments in the URL, resolves the host to public addresses, pins DNS for each attempt, and does not follow redirects.

Choose one scope:

• Team observes eligible events across the team, constrained by the subscription owner's current access.
• Collection observes the selected collection and every descendant collection.

Select one or more event types. Include agent events is off by default to prevent an agent from automatically retriggering itself. Enable it only when the consumer has an explicit loop-prevention rule.

Save the signing secret

Quire shows a whsec_… signing secret once when you create a subscription. Store it in your receiving service's secret manager. List and detail screens do not expose it again.

Rotating the secret immediately replaces the value used by future attempts, including retries of an existing delivery. Update the receiver before or at the same time as rotation.

Ownership and access

A member sees and manages only subscriptions they created. A team owner can manage all team subscriptions and sees each subscription owner.

Events and delivery attempts remain constrained to what the subscription owner may access. If that owner loses access to a collection or resource, pending attempts are canceled. Removing the owner from the team disables their subscriptions. Deleting a scoped collection disables subscriptions rooted there.

Disable a subscription to stop pending attempts without deleting its history. Deleting is soft: historical delivery records remain available during the retention window.