ESP (Klaviyo, Braze, HubSpot, SFMC)

Quick-start for the ESP (Klaviyo, Braze, HubSpot, SFMC) connector.

In this demo build the ESP (Klaviyo, Braze, HubSpot, SFMC) connector uses a recorded-fixture transport: payloads have the platform's public API shape, but nothing leaves the server and no credential exists.

At a glance

Connector id

esp

Kinds

esp

Capabilities

send signals

Authentication

api key

Rate limits

Per vendor

Mechanism

Template blocks and segments

Quick-start

1. Create a read-only API key on the platform and paste the key and secret.
2. Run the first import. Records are staged first; review the validation summary and any conflicts with your own overrides.
3. Keep it current: re-import on a schedule or when the source changes.
4. Publish. Every projection is validated before it goes live.

curl -s https://app.fondaq.ai/v1/merchants/$MID/connections -H "Authorization: Bearer $AGORA_API_KEY" \
  -H "Agora-Version: 2026-10-25" -H "Idempotency-Key: connect-esp-001" -H 'Content-Type: application/json' \
  -d '{ "method": "esp" }'

Notes

Lifecycle machine layer; interface implemented against a fixture in the demo

Source: connector registry (platform/connectors listConnectors())