Mint an aggregator webhook token

Mints a webhook token bound to an existing aggregator connection and returns the raw token plus its provider-facing webhook URL ONCE. Only the token’s SHA-256 hash is stored. This route does not deduplicate retries. Resending it, even with the same X-Idempotency key, mints another credential.

POST /v1/discovery/webhooks/tokens

Mint an aggregator webhook token

cURL

curl --request POST \
  --url https://matcher.sandbox.lerian.net/v1/discovery/webhooks/tokens \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "connection_config_name": "pluggy-main",
  "vendor": "pluggy"
}
'

201

Example

{
  "token": "<string>",
  "vendor": "pluggy",
  "webhook_url": "<string>"
}

Autorizaciones

Authorization · string · header · requerido

Bearer token authentication (format: "Bearer {token}")

Cuerpo

application/json

connection_config_name · string · requerido

Config name of the existing aggregator connection the token binds to

Minimum string length: 1

Ejemplo:

"pluggy-main"

vendor · enum<string> · requerido

Aggregator vendor the token is minted for: pluggy (Pluggy) or belvo (Belvo)

Opciones disponibles: pluggy, belvo

Ejemplo:

"pluggy"

Respuesta

201

application/json

Created

token · string · requerido

Raw bearer token, surfaced exactly once; only its SHA-256 hash is stored server-side

vendor · enum<string> · requerido

Aggregator vendor the token is bound to

Opciones disponibles: pluggy, belvo

Ejemplo:

"pluggy"

webhook_url · string · requerido

Fully-formed provider-facing receiver URL embedding the raw token in its path segment; configure this in the vendor dashboard