Census Reverse ETL API
Provides programmatic control over Census Reverse ETL syncs, enabling agents to trigger syncs, monitor run status, and manage the pipelines that push data warehouse records into CRMs, ad platforms, and other business destinations.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
API keys lack granular scopes, granting full workspace control. Destination OAuth tokens and credentials are managed by Census and not exposed via the API. TLS enforced on all endpoints.
⚡ Reliability
Best When
Best when an agent needs to orchestrate data activation from a warehouse to downstream business tools, especially when tight integration with dbt models and CI/CD pipelines is required.
Avoid When
Avoid when you need to load data into a warehouse rather than out of it, or when real-time event delivery to destinations is required rather than periodic batch syncs.
Use Cases
- • Trigger a Census sync after a dbt model refresh completes to ensure Salesforce lead scores reflect the latest warehouse data
- • Poll sync run status and surface failures to a Slack alerting pipeline when audience exports to Google Ads fall behind
- • List all configured syncs with their last-run status to generate a daily data freshness audit for the data team
- • Pause all syncs targeting a specific destination before a credential rotation and resume them after validation
- • Programmatically create or update sync configurations as part of an Infrastructure-as-Code data activation workflow
Not For
- • Ingesting data into a warehouse — Census is reverse ETL (warehouse to business tools), not forward ETL; use Airbyte or Fivetran to load data into the warehouse
- • Real-time streaming data pipelines — Census operates on scheduled or triggered batch syncs, not sub-second event streams
- • Direct SQL execution against your warehouse — Census orchestrates syncs but does not expose a query interface; connect directly to the warehouse for ad-hoc queries
Interface
Authentication
API key authentication via Bearer token in the Authorization header. Keys are generated per workspace in the Census UI. No granular scopes — a key grants full access to the workspace.
Pricing
Pricing details require contacting Census for Business and Enterprise tiers. Free tier available for initial evaluation.
Agent Metadata
Known Gotchas
- ⚠ Triggering a sync while a run is already active may queue a second run depending on sync configuration — agents must check current run state before triggering to avoid duplicate data pushes to destinations
- ⚠ Sync failures caused by destination credential expiration (e.g., expired OAuth token for Salesforce) look identical to data errors in the API response; root cause requires inspecting error message text
- ⚠ The management API controls sync orchestration but does not expose the underlying warehouse query or model logic — debugging data quality issues requires separate access to the warehouse
- ⚠ Webhook payloads for sync completion events may arrive before the run status is fully updated in the REST API, causing a race condition if agents query status immediately after receiving a webhook
- ⚠ API keys are workspace-scoped without granular permissions, meaning a single key can trigger, pause, or delete any sync — agents should use dedicated keys with documented access scope
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Census Reverse ETL API.
Scores are editorial opinions as of 2026-03-06.