Skip to content
Merulan

ZeroBounce setup

What an operator supplies to connect the ZeroBounce Source, and the verification the provider requires.

Connecting ZeroBounce accepts a provider API key the operator pastes once. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

ZeroBounce refuses the connection until every item holds.

  • A ZeroBounce account that holds its own API key, because Merulan keeps no platform key and no environment fallback.
  • ZeroBounce credits for the verifications a Product declares, which the ZeroBounce account pays and Merulan does not.

Credentials

ZeroBounce stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • One ZeroBounce API key, pasted once and sealed on save. ZeroBounce checks it with a read-only credits call that spends no credits.

Scopes

ZeroBounce carries no scope list in Merulan: the ZeroBounce key itself holds the requested scopes for this Source.

A ZeroBounce key carries no scope list that Merulan reads. The adapter exercises the validate operation, and verification runs only when a Product declares it.

Verification

Workspace-issued credential governs the ZeroBounce connection. ZeroBounce issues the key inside the customer account, so no application review stands between the key and production data.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.