Skip to main content

Webhook Subscriptions

The VQ API supports creating, listing, and deleting account-scoped webhook subscriptions. Configure the destination, event types, and optional symbol filter before delivery is enabled.
Subscription management is being rolled out and may not yet be available on production. Core does not currently deliver events or provide a streaming listener. A successful subscription response does not mean notifications will be sent.

Accepted Event Identifiers

These are accepted when creating a subscription. They are not delivered until the event-delivery service is released.

Create a Subscription

The destination must use HTTPS, must not contain embedded credentials, and must resolve to public IP addresses. Each account can create up to 10 subscriptions. A subscription can filter to at most 100 symbols.

Signature Verification Preparation

The SDKs include HMAC verification helpers for clients preparing a receiver. Core does not currently send webhook deliveries, so there are no live signatures to verify yet. The SDK verification helpers expect these headers on a future signed delivery. Core does not currently emit them:

Verify a Future Delivery

Planned Event Payload Shape

Managing Webhooks

List responses do not include signing secrets. There is no update or secret-rotation endpoint; delete and recreate a subscription if its URL or configuration must change.

Best Practices

  1. Use an HTTPS endpoint that resolves to public IP addresses.
  2. Store the creation secret in a secret manager; it is not returned by list.
  3. Keep subscription management separate from event-processing readiness; delivery is not active yet.
  4. Do not assume a retry policy, delivery cadence, or event payload guarantee until those are published with the delivery rollout.