v1

latestOpenAPI 3.1.02026-07-263644911022.4 KB
Discovery

Receive an aggregator webhook

Receives a Pluggy/Belvo aggregator webhook and asynchronously pulls the signaled data into the ingestion pipeline. This route carries no operator JWT. It is authenticated by an opaque token in the URL path (resolved to a tenant binding server-side, never claimed) PLUS a per-provider source check: a valid HMAC-SHA256 of the raw body in the X-Webhook-Signature header, OR membership in the provider's source-IP allowlist. Both layers fail closed; the tenant is derived solely from the resolved token binding.

post/v1/discovery/webhooks/{provider}/{webhookToken}

Path parameters

providerstring required

Aggregator provider the token was minted for (pluggy or belvo)

Example:pluggy

Aggregator provider the token was minted for (pluggy or belvo)

webhookTokenstring required

Opaque webhook token minted for the connection; hashed and resolved to a tenant binding server-side

Opaque webhook token minted for the connection; hashed and resolved to a tenant binding server-side

Headers

X-Webhook-Signaturestring

Hex HMAC-SHA256 of the raw body for signing providers; omitted by IP-allowlist providers

Hex HMAC-SHA256 of the raw body for signing providers; omitted by IP-allowlist providers

Response

Accepted