Skip to content
Merulan

Apollo setup

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

Connecting Apollo 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

Apollo refuses the connection until every item holds.

  • An Apollo account that holds its own API key, because Merulan keeps no platform key and no environment fallback.
  • Apollo credits for the lookups a Product runs, which the Apollo account pays and Merulan does not.

Credentials

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

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

Scopes

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

An Apollo key carries no scope list that Merulan reads. The adapter exercises the people match operation, so narrow the account rather than the key.

Verification

Workspace-issued credential governs the Apollo connection. Apollo 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.